Bernie,
I tried it from R> and all was fine. The block being called is the first
in the APX file... maybe that makes a difference.
I can't think of anything else that would make it work. I use RClass
to assemble cmd files to an APP, but I don't think that would help.
When Dennis added the ability for RClass to support 'quit to' he
mentioned it was a new functionality for RBase under codelocked
files.. this prior to the release of 6.5.
Maybe RBTI could chime in and clarify which versions support 'quit
to' in codelocked files and under what conditions if not fully.
Ben Petersen
On 1 Sep 2001, at 0:38, Bernie Corrigan wrote:
> Ben -
>
> This must be a runtime thing. I can't get it to work in regular old
> RBase 6.5++. Keep getting the same error message.
>
> Bernie
> =======================================
> At 07:27 PM 8/31/2001 +0100, you wrote:
> >Bernie,
> >
> >The line is: "quit to BT in BTW.apx"
> >This is executed from DATAX.apx
> >
> >I actually thought I had used this more often... I think I changed
> >some instances to make for easier testing. These particular files
> >are running at 5 different sites under 6.1a runtime, and at a sixth
> >under 6.5+. The sixth site is having problems, but not at this
> >particular point, and we haven't determined if the actual problem is
> >R:Base related or not.
> >
> >Ben Petersen
> >
> >
> >On 31 Aug 2001, at 17:41, Bernie Corrigan wrote:
> >
> >> Ben -
> >>
> >> We must have different versions of RBase for Windows. The results I
> >> get for the command
> >>
> >> QUIT TO command_block_name IN proc_name.apx
> >>
> >> are:
> >>
> >> Windows 6.1A: -ERROR- Syntax is incorrect for the command.
> >>
> >> Windows 6.5: -ERROR- Syntax is incorrect for the command. (2045)
> >>
> >> Windows 6.5++: -ERROR- Syntax is incorrect for the command QUIT. (2045)
> >>
> >> R:Syntax shows this QUIT TO command to be valid but it isn't working here.
> >>
> >>
> >> RUN command_block_name IN proc_name.apx
> >>
> >> works just fine for the same files.
> >>
> >> Please test this and let me know if you are getting different
> >> results with 6.5++. This particular item was on my wish list of
> >> improvements for 6.5++.
> >>
> >> Bernie
> >> =======================================
> >> At 02:22 PM 8/31/2001 +0100, you wrote:
> >> >Bernie,
> >> >
> >> >quit to CmdBlock in YourApp.apx has worked fine for me in 6.1a
> >> >and I _think_ in 6.5+
> >> >
> >> >Ben Petersen
> >> >
> >> >
> >> >On 31 Aug 2001, at 11:26, Bernie Corrigan wrote:
> >> >
> >> >> J.M. -
> >> >>
> >> >> That command simply doesn't work when you are attempting to
> QUIT TO
> >> >> a command file within a procedure file. The technique I use is to
> quit to
> >> >> a one line command file which then RUNs the command file in the procedure
> >> >> file. You can QUIT TO single codelocked command files but not to command
> >> >> files within codelocked procedure files.
> >> >>
> >> >> Bernie
> >> >> =======================================
> >> >> At 07:14 AM 8/31/2001 -0400, you wrote:
> >> >> >
> >> >> >Hi all,
> >> >> >
> >> >> >I know that this topic has been discused already ...
> >> >> >
> >> >> >I try to use rbw6.5++ new command QUIT TO BlockName IN ProcName, and
> I get
> >> >> >:
> >> >> >'Syntax is incorrect for the command QUIT (2045)'
> >> >> >
> >> >> >Is there anybody that could help ?
> >> >> >
> >> >> >Here is what I am doing :
> >> >> >
> >> >> >I have a command file named DAU.RMD :
> >> >> >
> >> >> >$COMMAND
> >> >> >DAU
> >> >> >*( Comments .....)
> >> >> >SET error var varr
> >> >> >....
> >> >> >Code
> >> >> >....
> >> >> >RETURN
> >> >> >
> >> >> >I codelock it using option 5, name of the codelocked file is DAU.APX
> >> >> >
> >> >> >Then I enter :
> >> >> >
> >> >> >QUIT TO dau IN dau.apx
> >> >> >
> >> >> >And I get the above error message ....
> >> >> >
> >> >> >Same problem when codelocked with option 1
> >> >> >
> >> >> >No problem when the same codelocked file is run with :
> >> >> >
> >> >> >RUN dau IN dau.apx
> >> >> >
> >> >> >Is it a bug ? or am I doing something wrong ?
> >> >> >
> >> >> >TIA
> >> >> >
> >> >> >
> >> >> >J.M. GRATIAS, Logimatique, France
> >> >> >
> >> >>
> >> >>
> >> >
> >> >
> >> >
> >>
> >>
> >
> >
> >
>
>
