How to disable Compiling from the WED Editor in AccuTerm
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
We are using jBASE 5.6 multivalue database. Is there a way to disable the fact that AccuTerm's WED Editor has the ability to compile programs in the underlying MultiValue database? We are running into an issue where the user is accidentally compiling records instead of programs, which creates corrupt records in the datafiles.
I believe there is also a shortcut key (Function Key) that is in use. Help!
multivalue pick jbase
add a comment |
We are using jBASE 5.6 multivalue database. Is there a way to disable the fact that AccuTerm's WED Editor has the ability to compile programs in the underlying MultiValue database? We are running into an issue where the user is accidentally compiling records instead of programs, which creates corrupt records in the datafiles.
I believe there is also a shortcut key (Function Key) that is in use. Help!
multivalue pick jbase
Hi Welcome to stackoverflow. it would be great if you would read How to ask a question first before posting. Thanks!
– Nico
Nov 16 '18 at 18:43
1
Hi @Nico, what was wrong with my question? I should have asked a question-format in the title, but other than that, any help?
– J.Camacho
Nov 16 '18 at 22:33
add a comment |
We are using jBASE 5.6 multivalue database. Is there a way to disable the fact that AccuTerm's WED Editor has the ability to compile programs in the underlying MultiValue database? We are running into an issue where the user is accidentally compiling records instead of programs, which creates corrupt records in the datafiles.
I believe there is also a shortcut key (Function Key) that is in use. Help!
multivalue pick jbase
We are using jBASE 5.6 multivalue database. Is there a way to disable the fact that AccuTerm's WED Editor has the ability to compile programs in the underlying MultiValue database? We are running into an issue where the user is accidentally compiling records instead of programs, which creates corrupt records in the datafiles.
I believe there is also a shortcut key (Function Key) that is in use. Help!
multivalue pick jbase
multivalue pick jbase
edited Nov 16 '18 at 22:34
Mike Wright
6018
6018
asked Nov 16 '18 at 18:14
J.CamachoJ.Camacho
113
113
Hi Welcome to stackoverflow. it would be great if you would read How to ask a question first before posting. Thanks!
– Nico
Nov 16 '18 at 18:43
1
Hi @Nico, what was wrong with my question? I should have asked a question-format in the title, but other than that, any help?
– J.Camacho
Nov 16 '18 at 22:33
add a comment |
Hi Welcome to stackoverflow. it would be great if you would read How to ask a question first before posting. Thanks!
– Nico
Nov 16 '18 at 18:43
1
Hi @Nico, what was wrong with my question? I should have asked a question-format in the title, but other than that, any help?
– J.Camacho
Nov 16 '18 at 22:33
Hi Welcome to stackoverflow. it would be great if you would read How to ask a question first before posting. Thanks!
– Nico
Nov 16 '18 at 18:43
Hi Welcome to stackoverflow. it would be great if you would read How to ask a question first before posting. Thanks!
– Nico
Nov 16 '18 at 18:43
1
1
Hi @Nico, what was wrong with my question? I should have asked a question-format in the title, but other than that, any help?
– J.Camacho
Nov 16 '18 at 22:33
Hi @Nico, what was wrong with my question? I should have asked a question-format in the title, but other than that, any help?
– J.Camacho
Nov 16 '18 at 22:33
add a comment |
1 Answer
1
active
oldest
votes
As of AccuTerm Release 7.3a there is no explicit option to disable the compile shortcut in the AccuTerm wED (Windows Editor). There are two techniques you can apply, however, that will work:
- Change the Compile command to a single space
- Open the wED
- Click on the Tools menu at the top
- Click on Settings
- Click on the Tools tab
- In the Compile section, change the text in the Command input from BASIC to a single space. Note that some flavors of PICK use BASIC as the compilation command whereas others use COMPILE. Since you are running jBASE, BASIC applies in this instance but for others such as D3 the command to replace is COMPILE.
- Open the wED
- It is possible to write a wrapper program to handle compilation for you, which when cataloged could be called from this same Command input. That program could be written to decide whether or not the target record exists in a code file or a data file and then compile or skip, respectively. Due to the fact that PICK systems do not have a file type specification, this logic would be somewhat unique to your environment depending on your practices. Common practice is to denote code files as BP files, i.e. FileNameBP or FileName.BP but again it would depend on your implementation.
For the record, a request to have a more formal option for disabling the Compile command has been submitted to the AccuTerm development team for consideration in the next major release.
Thanks @MikeWright! This was exactly what I was looking for, since clearing out the field of the "Compile" set it back to something else (i.e., it has to have something in there)
– J.Camacho
Nov 16 '18 at 22:37
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53343320%2fhow-to-disable-compiling-from-the-wed-editor-in-accuterm%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
As of AccuTerm Release 7.3a there is no explicit option to disable the compile shortcut in the AccuTerm wED (Windows Editor). There are two techniques you can apply, however, that will work:
- Change the Compile command to a single space
- Open the wED
- Click on the Tools menu at the top
- Click on Settings
- Click on the Tools tab
- In the Compile section, change the text in the Command input from BASIC to a single space. Note that some flavors of PICK use BASIC as the compilation command whereas others use COMPILE. Since you are running jBASE, BASIC applies in this instance but for others such as D3 the command to replace is COMPILE.
- Open the wED
- It is possible to write a wrapper program to handle compilation for you, which when cataloged could be called from this same Command input. That program could be written to decide whether or not the target record exists in a code file or a data file and then compile or skip, respectively. Due to the fact that PICK systems do not have a file type specification, this logic would be somewhat unique to your environment depending on your practices. Common practice is to denote code files as BP files, i.e. FileNameBP or FileName.BP but again it would depend on your implementation.
For the record, a request to have a more formal option for disabling the Compile command has been submitted to the AccuTerm development team for consideration in the next major release.
Thanks @MikeWright! This was exactly what I was looking for, since clearing out the field of the "Compile" set it back to something else (i.e., it has to have something in there)
– J.Camacho
Nov 16 '18 at 22:37
add a comment |
As of AccuTerm Release 7.3a there is no explicit option to disable the compile shortcut in the AccuTerm wED (Windows Editor). There are two techniques you can apply, however, that will work:
- Change the Compile command to a single space
- Open the wED
- Click on the Tools menu at the top
- Click on Settings
- Click on the Tools tab
- In the Compile section, change the text in the Command input from BASIC to a single space. Note that some flavors of PICK use BASIC as the compilation command whereas others use COMPILE. Since you are running jBASE, BASIC applies in this instance but for others such as D3 the command to replace is COMPILE.
- Open the wED
- It is possible to write a wrapper program to handle compilation for you, which when cataloged could be called from this same Command input. That program could be written to decide whether or not the target record exists in a code file or a data file and then compile or skip, respectively. Due to the fact that PICK systems do not have a file type specification, this logic would be somewhat unique to your environment depending on your practices. Common practice is to denote code files as BP files, i.e. FileNameBP or FileName.BP but again it would depend on your implementation.
For the record, a request to have a more formal option for disabling the Compile command has been submitted to the AccuTerm development team for consideration in the next major release.
Thanks @MikeWright! This was exactly what I was looking for, since clearing out the field of the "Compile" set it back to something else (i.e., it has to have something in there)
– J.Camacho
Nov 16 '18 at 22:37
add a comment |
As of AccuTerm Release 7.3a there is no explicit option to disable the compile shortcut in the AccuTerm wED (Windows Editor). There are two techniques you can apply, however, that will work:
- Change the Compile command to a single space
- Open the wED
- Click on the Tools menu at the top
- Click on Settings
- Click on the Tools tab
- In the Compile section, change the text in the Command input from BASIC to a single space. Note that some flavors of PICK use BASIC as the compilation command whereas others use COMPILE. Since you are running jBASE, BASIC applies in this instance but for others such as D3 the command to replace is COMPILE.
- Open the wED
- It is possible to write a wrapper program to handle compilation for you, which when cataloged could be called from this same Command input. That program could be written to decide whether or not the target record exists in a code file or a data file and then compile or skip, respectively. Due to the fact that PICK systems do not have a file type specification, this logic would be somewhat unique to your environment depending on your practices. Common practice is to denote code files as BP files, i.e. FileNameBP or FileName.BP but again it would depend on your implementation.
For the record, a request to have a more formal option for disabling the Compile command has been submitted to the AccuTerm development team for consideration in the next major release.
As of AccuTerm Release 7.3a there is no explicit option to disable the compile shortcut in the AccuTerm wED (Windows Editor). There are two techniques you can apply, however, that will work:
- Change the Compile command to a single space
- Open the wED
- Click on the Tools menu at the top
- Click on Settings
- Click on the Tools tab
- In the Compile section, change the text in the Command input from BASIC to a single space. Note that some flavors of PICK use BASIC as the compilation command whereas others use COMPILE. Since you are running jBASE, BASIC applies in this instance but for others such as D3 the command to replace is COMPILE.
- Open the wED
- It is possible to write a wrapper program to handle compilation for you, which when cataloged could be called from this same Command input. That program could be written to decide whether or not the target record exists in a code file or a data file and then compile or skip, respectively. Due to the fact that PICK systems do not have a file type specification, this logic would be somewhat unique to your environment depending on your practices. Common practice is to denote code files as BP files, i.e. FileNameBP or FileName.BP but again it would depend on your implementation.
For the record, a request to have a more formal option for disabling the Compile command has been submitted to the AccuTerm development team for consideration in the next major release.
answered Nov 16 '18 at 20:53
Mike WrightMike Wright
6018
6018
Thanks @MikeWright! This was exactly what I was looking for, since clearing out the field of the "Compile" set it back to something else (i.e., it has to have something in there)
– J.Camacho
Nov 16 '18 at 22:37
add a comment |
Thanks @MikeWright! This was exactly what I was looking for, since clearing out the field of the "Compile" set it back to something else (i.e., it has to have something in there)
– J.Camacho
Nov 16 '18 at 22:37
Thanks @MikeWright! This was exactly what I was looking for, since clearing out the field of the "Compile" set it back to something else (i.e., it has to have something in there)
– J.Camacho
Nov 16 '18 at 22:37
Thanks @MikeWright! This was exactly what I was looking for, since clearing out the field of the "Compile" set it back to something else (i.e., it has to have something in there)
– J.Camacho
Nov 16 '18 at 22:37
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53343320%2fhow-to-disable-compiling-from-the-wed-editor-in-accuterm%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Hi Welcome to stackoverflow. it would be great if you would read How to ask a question first before posting. Thanks!
– Nico
Nov 16 '18 at 18:43
1
Hi @Nico, what was wrong with my question? I should have asked a question-format in the title, but other than that, any help?
– J.Camacho
Nov 16 '18 at 22:33