You can also store each of your $Command blocks right in the database as
VarChar data and use the Run Select command to execute the code without the
exposure of a disk file.
----- Original Message -----
From: "Ed Rivkin" <[email protected]>
To: "RBASE-L Mailing List" <[email protected]>
Sent: Monday, April 20, 2009 1:42 PM
Subject: [RBASE-L] - RE: 4.5 -
7.6ApplicationConversionQuestion/Considerations
Mike,
What I am trying to do is keep my .apx file mostly intact
rather than breaking it up into many small .rmd files or
cutting/pasting it into a form or .rba.
What Hartmut suggested was a mechanism for doing this.
Based on your question and syntax below, I looked at the
.app again and quickly realized my mistake.
The &command in the .app should be $command.
Thanks to both of you for the help. I am dangerous again.
Ed
Apr 20, 2009 12:20:33 PM, [email protected] wrote:
If ACT01 is a custom action in the RBA, why are you calling it in
Propman.apx via: RUN act01 IN Propman.apx. Does ACT01 exist as a procedure
in PropMan.apx like this:
$COMMAND
ACT01
-- buncho of code
RETURN
----- Original Message -----
From: "Ed Rivkin" <[email protected]>
To: "RBASE-L Mailing List" <[email protected]>
Sent: Monday, April 20, 2009 1:05 PM
Subject: [RBASE-L] - RE: 4.5 - 7.6
ApplicationConversionQuestion/Considerations
Hartmut,
Yes. That is the option that I took; .
PROPMAN.APP
PROPMAN.APX
I also deleted the previous PROPMAN.APX before compiling.
.app file is 25k
.apx file is 3k
Any other thoughts?
Ed
Apr 20, 2009 11:45:18 AM, [email protected] wrote:
Ed,
have you done:
Codelock 5 PROPMAN.app PROPMAN.apx ?
Codelock 5 makes the run procedure. All the others is o.k.
Hartmut
Ed Rivkin schrieb:
> John and Hartmut,
> Thanks for the replies. Because of the large quantity of menu options in
my
> original application,
> I decided to opt for a new application file with calls to the revised
"pre-Rbase
> 7" application
> file per Hartmut's suggestion.
>
> Something isn't working for me. I am getting the error, "Error- Not a
run
> procedue (567)" when
> I try to execute the menu options in the new .rba application linking
back to
> the modified .apx
>
> Here's what I've done. I will use my first action for illustration
purposes.
> My original .app is PROPMAN
>
> 1) Edited PROPMAN and removed all code prior to first desired action
>
> 2) Inserted into PROPMAN before the first desired action
> &Command
> Act01
> .......
> 3) Inserted into PROPMAN after the first desired action
> Return
>
> 4) Codelock the PROPMAN.app into PROPMAN.apx
>
> 5) Created .rba using Application Designer
>
> 6) First Action in the new .rba is ACT01 and is a Custom Action
> It is:
> RUN act01 IN Propman.apx
> RETURN
>
> It appears as RUNAct01.$$$
> when viewing Action 01. If I edit the Custom action it
> reads correctly as indicated above in this item.
>
> Any thoughts as to why I am getting the "Error - Not a Run Procedure"?
>
> Other Actions in the .rba go directly to .rmd files and work fine.
>
> Thanks in advance,
> Ed
>
> Apr 17, 2009 08:01:39 AM, [email protected] [email protected]> wrote:
>
> Ed,
> I have converted my big 6.5 app's to 7.6 by making single actions from
> each vpick, such as:
>
> &COMMAND
> act01
> ....
> RETURN
>
> for all CASE and pack it together in a new app. In the rba you only run
> the action from the apx:
>
> RUN act01 IN test.apx
> RETURN
>
> It works faster, because the rba's are small without the code. And you
> can better read the code at all in an app-file as in the single menu
> items of the rba.
>
> Hartmut Braun
>
> John Engwer schrieb:
> > Ed,
> >
> >
> >
> > I have converted quite a few applications and my opinion is that it is
> worth the effort to move all of the code into your forms from the
beginning.
> In most cases it is not a very difficult; you should be able to create a
> main menu form then cut and paste most the code into your form from your
> application.
> >
> >
> >
> > John
> >
> >
> >
> > From: [email protected] [email protected]>
> [mailto:[email protected] [email protected]>] On Behalf Of
> [email protected] [email protected]>
> > Sent: Thursday, April 16, 2009 11:11 PM
> > To: RBASE-L Mailing List
> > Subject: [RBASE-L] - 4.5 - 7.6 Application Conversion
Question/Considerations
> >
> >
> >
> > Hello Rbase-l,
> > I am converting/migrating an application from R:Base 4.5 to Windows
7.6.
> I think that most
> > of the forms, reports, and labels are now successfully migrated. Along
> the way I am trying
> > to take advantage of much of the new functionality to improve user
> navigation and data
> > quality/integrity. There is a LOT of good function in 7.6.
> >
> > I have one forms question that I will enter in a subsequent post to
the
> forum.
> >
> > In my 4.5 application I used numerous external .cmd files and those
have
> been converted.
> > Most of the issues were screen handling (converting Write and Fillin
to
> Pause and Dialog)
> > and printer parameters.
> >
> > The final challenge is the .app file. Walking through the Application
> Build tutorial today
> > and evaluating the Forms options, it looks like creating an
application
> .rba file makes the
> > most sense for my environment.
> >
> > I am having a problem "putting it all together". Is there a method to
> convert my current
> > .app file to an .rba. I understand that the afore mentioned screen
> handling and printer
> > commands need to be updated. My current app is about 750 lines of code
> and I would
> > like to take advantage of much of it as practical without a total
re-do.
> >
> > I am curious what others on the forum have done in these circumstances
> and if you
> > could point me to any documentation or examples. I have been through
the
> "Getting
> > Started, DB Conversion Guide, Edge articles, Tutorial, and Sample
apps.
> >
> > Thanks in advance for any assistance.
> >
> > Take care,
> > Ed Rivkin
> >
> >
>
> ____________
> Virus checked by G DATA AntiVirus
> Version: AVK 19.4643 dated 15.04.2009
>
>
____________
Virus checked by G DATA AntiVirus
Version: AVK 19.4702 dated 18.04.2009
