Hello David: I am leaning towards using standalone files in separate subdirectories, this way I keep them away from the main directory; it seems that it would work better for the type of applications I have although the file path length is a concern for EEPs (I understand this is being corrected). One quick comment, I have done away with the Manu files; I store the menu options in tables within the database and I just use the CHOOSE command to select the rows I want displayed. With the availability of the TITLE and CAPTION options for the CHOOSE command, it has simplified coding vis-�-vis the old DOS coding. This approach works wonderfully and it is very easy to maintain. Thanks for the information,
Javier Valencia, PE President Valencia Technology Group, L.L.C. 14315 S. Twilight Ln., Suite #14 Olathe, KS 66062-4571 (913)829-0888 (913)649-2904 FAX -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of David M. Blocker Sent: Tuesday, August 20, 2002 8:12 AM To: [EMAIL PROTECTED] Subject: Re: Rbase momenclature and codelock issues Hi Javier Because of the time involved in codelocking all the time, I usually rely on standalone ascii command files for applications I develop. Sometimes I inherit APX style programs with a client who had someone else develop the original application and I stick with it, but I always find it simpler to have many files that are easily accessible. The down side of course is all those files! But I regularly use PKZIP to keep an updated master single file of all programs. Extensions I use are: filename.dat startup file filename.RMD macros, programs filename.ENP row or field entry procedure filename.EXP row or field exit procedure filename.MNU menu files (for CHOOSE) David Blocker ----- Original Message ----- From: "Javier Valencia" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, August 19, 2002 9:54 PM Subject: RE: Rbase momenclature and codelock issues > Hello Tom: > Thank you very much for the feedback; I am trying to standardize my code > (and nomenclature) as much as I can. In this particular issue, there are > advantages and disadvantages to each approach and I am trying to get a feel > for what other developers experience has been. The beauty of the list is > that you get feedback from actual users and developers with extensive > experience, rather that a reviewer that has worked with the software for a > few hours. > Your comments are greatly appreciated and I will definitely use the > information provided. > Thanks again, > > Javier Valencia, PE > President > Valencia Technology Group, L.L.C. > 14315 S. Twilight Ln., Suite #14 > Olathe, KS 66062-4571 > (913)829-0888 > (913)649-2904 FAX > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On > Behalf Of Tom Grimshaw > Sent: Monday, August 19, 2002 9:09 PM > To: [EMAIL PROTECTED] > Subject: Re: Rbase momenclature and codelock issues > > G'day Javier, > > I have diametrically opposed views to some I have discussed this with and > therefore offer what I do personally not as gospel but as one way of doing > things. > > I have one or two main files into which I put all my code blocks for each > module. > > For instance I have one called MoneyMgr.app which contains 5340 lines of > code > and 44 $COMMAND blocks. > > I prefer this over having each block in its own file as I find it far > faster to > find another block in a file rather than opening another file. > > The exception to this are user interface functions and those called from > more > than one module. For this I have a UI.apx and GlobBlok.apx file into which > I put those blocks. > > BizMan now has about 94 app files (and consequently 94 apx files) and I find > most of my work normally revolves around one module at a time so the above > methodology is reasonably efficient and convenient for me. > > Hope this helps. > > At 17:11 19/08/02 -0500, you wrote: > > >Is there an official nomenclature for naming files (extension) that are > >used with Rbase.? I am in the process of converting a large application > >from Rbase 4.5++ DOS to Rbase 6.5++ for Windows and this would be a good > >time to rename files if necessary. > > Warmest regards, > > > Tom Grimshaw > coy: Just For You Software > tel: 612 9552 3311 > fax: 612 9566 2164 > mobile: 0414 675 903 > > post: PO Box 470 Glebe NSW 2037 Australia > street: 3/66 Wentworth Park Rd Glebe NSW 2037 > > email: [EMAIL PROTECTED] > web: www.just4usoftware.com.au > > "... the control of impulse -- is the first principle of civilization."-- > Will Durant, > Pulitzer Prize winning philosopher, writer and historian > > the most needed product in the world can be found at > www.thewaytohappiness.org > > This email and any files transmitted with it are confidential to the > intended recipient and may be privileged. If you have received this email > inadvertently or you are not the intended recipient, you may not > disseminate, distribute, copy or in any way rely on it. Further, you should > notify the sender immediately and delete the email from your computer. > Whilst we have taken precautions to alert us to the presence of computer > viruses, we cannot guarantee that this email and any files transmitted with > it are free from such viruses. > > ================================================ > TO SEE MESSAGE POSTING GUIDELINES: > Send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: INTRO rbase-l > ================================================ > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: UNSUBSCRIBE rbase-l > ================================================ > TO SEARCH ARCHIVES: > http://www.mail-archive.com/rbase-l%40sonetmail.com/ > > ================================================ > TO SEE MESSAGE POSTING GUIDELINES: > Send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: INTRO rbase-l > ================================================ > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: UNSUBSCRIBE rbase-l > ================================================ > TO SEARCH ARCHIVES: > http://www.mail-archive.com/rbase-l%40sonetmail.com/ > ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/ ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
