The short answer is NO. At 05:11 PM 8/19/2002 -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. >Having started with Rbase 4000 back in 1986 I have used the following >extensions: >filename.dat Startup files >filename.asc, filename.txt ascii or text command files >filename.app application files >filename.apx codelocked application files >filename.rex codelocked executable files >Also, in the past I have stored all the codelocked files in a few large >procedure files, by using the option "ADD AN ASCII COMMAND FILE TO A >PROCEDURE FILE' (also, menus and screens). The problem that I had in the >past is that when I needed to re-codelock one file, the procedure file kept >getting larger and larger as the old code apparently was not erased. I would >have to delete the *.apx file and codelock all the files all over again (I >store the commands in an executable file) >Then, to run the particular program I would just code in a program something >like >: >Run utility1 in myutilities.apx > >The problem with this approach is that several clients have variations of >the individual files and every time I make a change I would have to >re-codelock all the files in the application (to reduce size) making it >difficult to keep track of the modifications. The approach that I am >considering using is to individually codelock the programs and place them in >separate subdirectories (one for utilities, one for epps, etc.); this way, >if I need to modify one file I only need to re-codelock the one file. >Any comment about these approaches? >One more issue, is it better to codelock an individual file as part of a >procedure file or as binary command file? For example, if I have a utility >to count widgets, (count_widg.txt) Is it better to codelock it to run as: > >RUN count_widg in utilities\count_widg.apx ==> (executable in a >procedure) >OR >RUN utilities\count_widg.rex ==> (codelocked executable file) > >Are there commands that will not run when codelocked? > >Any comment will be greatly appreciated. > > >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 > ><html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40";> > ><head> ><meta http-equiv=Content-Type content="text/html; charset=iso-8859-1"> ><meta name=ProgId content=Word.Document> ><meta name=Generator content="Microsoft Word 9"> ><meta name=Originator content="Microsoft Word 9"> ><link rel=File-List href="cid:[EMAIL PROTECTED]";> ><!--[if gte mso 9]><xml> > <o:OfficeDocumentSettings> > <o:DoNotRelyOnCSS/> > </o:OfficeDocumentSettings> ></xml><![endif]--><!--[if gte mso 9]><xml> > <w:WordDocument> > <w:View>Normal</w:View> > <w:Zoom>0</w:Zoom> > <w:DocumentKind>DocumentEmail</w:DocumentKind> > <w:EnvelopeVis/> > <w:DrawingGridHorizontalSpacing>2.5 pt</w:DrawingGridHorizontalSpacing> > <w:DrawingGridVerticalSpacing>5.1 pt</w:DrawingGridVerticalSpacing> > <w:DisplayHorizontalDrawingGridEvery>2</w:DisplayHorizontalDrawingGridEvery> > <w:DisplayVerticalDrawingGridEvery>2</w:DisplayVerticalDrawingGridEvery> > <w:Compatibility> > <w:SpaceForUL/> > <w:BalanceSingleByteDoubleByteWidth/> > <w:DoNotLeaveBackslashAlone/> > <w:ULTrailSpace/> > <w:DoNotExpandShiftReturn/> > <w:WW6BorderRules/> > <w:FootnoteLayoutLikeWW8/> > <w:ShapeLayoutLikeWW8/> > <w:AlignTablesRowByRow/> > <w:ForgetLastTabAlignment/> > <w:AutoSpaceLikeWord95/> > <w:DoNotUseHTMLParagraphAutoSpacing/> > <w:LayoutRawTableWidth/> > <w:LayoutTableRowsApart/> > </w:Compatibility> > </w:WordDocument> ></xml><![endif]--> ><style> ><!-- > /* Style Definitions */ >p.MsoNormal, li.MsoNormal, div.MsoNormal > {mso-style-parent:""; > margin:0in; > margin-bottom:.0001pt; > mso-pagination:widow-orphan; > mso-layout-grid-align:none; > punctuation-wrap:simple; > text-autospace:none; > font-size:12.0pt; > mso-bidi-font-size:10.0pt; > font-family:Arial; > mso-fareast-font-family:"Times New Roman";} >p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig > {margin:0in; > margin-bottom:.0001pt; > mso-pagination:widow-orphan; > mso-layout-grid-align:none; > punctuation-wrap:simple; > text-autospace:none; > font-size:12.0pt; > mso-bidi-font-size:10.0pt; > font-family:Arial; > mso-fareast-font-family:"Times New Roman";} >span.EmailStyle15 > {mso-style-type:personal-compose; > mso-ansi-font-size:10.0pt; > mso-ascii-font-family:Arial; > mso-hansi-font-family:Arial; > mso-bidi-font-family:Arial; > color:black;} >@page Section1 > {size:8.5in 11.0in; > margin:1.0in 1.0in 1.0in 1.5in; > mso-header-margin:.5in; > mso-footer-margin:.5in; > mso-paper-source:0;} >div.Section1 > {page:Section1;} >--> ></style> ></head> > ><body lang=EN-US style='tab-interval:.5in'> > ><div class=Section1> > ><p class=MsoNormal><span class=EmailStyle15><font size=2 color=black >face=Arial><span style='font-size:10.0pt'>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.<o:p></o:p></span></font></span></p> > ><p class=MsoNormal><span class=EmailStyle15><font size=2 color=black >face=Arial><span style='font-size:10.0pt'>Having started with Rbase 4000 back >in 1986 I have used the following extensions:<o:p></o:p></span></font></span></p> > ><p class=MsoNormal><span class=EmailStyle15><font size=2 color=black >face=Arial><span style='font-size:10.0pt'>filename.dat<span style='mso-tab-count: >2'> </span><span >style='mso-tab-count:1'> &nb sp; </span>Startup >files<o:p></o:p></span></font></span></p> > ><p class=MsoNormal><span class=EmailStyle15><font size=2 color=black >face=Arial><span style='font-size:10.0pt'>filename.asc, filename.txt<span >style='mso-tab-count:1'> &nb sp; </span>ascii >or text command files<o:p></o:p></span></font></span></p> > ><p class=MsoNormal><span class=EmailStyle15><font size=2 color=black >face=Arial><span style='font-size:10.0pt'>filename.app <span style='mso-tab-count: >3'> &nbs p; </span>application >files<o:p></o:p></span></font></span></p> > ><p class=MsoNormal><span class=EmailStyle15><font size=2 color=black >face=Arial><span style='font-size:10.0pt'>filename.apx<span style='mso-tab-count: >3'> &nbs p; </span>codelocked >application files<o:p></o:p></span></font></span></p> > ><p class=MsoNormal><span class=EmailStyle15><font size=2 color=black >face=Arial><span style='font-size:10.0pt'>filename.rex<span style='mso-tab-count: >3'> &nbs p; </span>codelocked >executable files<o:p></o:p></span></font></span></p> > ><p class=MsoNormal><span class=EmailStyle15><font size=2 color=black >face=Arial><span style='font-size:10.0pt'>Also, in the past I have stored all >the codelocked files in a few large procedure files, by using the option “ADD AN >ASCII COMMAND FILE TO A PROCEDURE FILE’ (also, menus and screens). The problem >that I had in the past is that when I needed to re-codelock one file, the >procedure file kept getting larger and larger as the old code apparently was >not erased. I would have to delete the *.apx file and codelock all the files >all over again (I store the commands in an executable file)<o:p></o:p></span></font></span></p> > ><p class=MsoNormal><span class=EmailStyle15><font size=2 color=black >face=Arial><span style='font-size:10.0pt'>Then, to run the particular program I >would just code in a program something like<o:p></o:p></span></font></span></p> > ><p class=MsoNormal><span class=EmailStyle15><font size=2 color=black >face=Arial><span style='font-size:10.0pt'>:<o:p></o:p></span></font></span></p> > ><p class=MsoNormal><span class=EmailStyle15><font size=2 color=black >face=Arial><span style='font-size:10.0pt'>Run utility1 in myutilities.apx<o:p></o:p></span></font></span></p> > ><p class=MsoNormal><span class=EmailStyle15><font size=2 color=black >face=Arial><span style='font-size:10.0pt'><![if !supportEmptyParas]> <![endif]><o:p></o:p></span></font></span></p> > ><p class=MsoNormal><span class=EmailStyle15><font size=2 color=black >face=Arial><span style='font-size:10.0pt'>The problem with this approach is >that several clients have variations of the individual files and every time I >make a change I would have to re-codelock all the files in the application (to >reduce size) making it difficult <span style="mso-spacerun: yes"> </span>to >keep track of the modifications. The approach that I am considering using is to >individually codelock the programs and place them in separate subdirectories >(one for utilities, one for epps, etc.); this way, if I need to modify one file >I only need to re-codelock the one file.<o:p></o:p></span></font></span></p> > ><p class=MsoNormal><span class=EmailStyle15><font size=2 color=black >face=Arial><span style='font-size:10.0pt'>Any comment about these approaches?<o:p></o:p></span></font></span></p> > ><p class=MsoNormal><span class=EmailStyle15><font size=2 color=black >face=Arial><span style='font-size:10.0pt'>One more issue, is it better to >codelock an individual file as part of a procedure file or as binary command >file? For example, if I have a utility to count widgets, (count_widg.txt) Is it >better to codelock it to run as:<o:p></o:p></span></font></span></p> > ><p class=MsoNormal><span class=EmailStyle15><font size=2 color=black >face=Arial><span style='font-size:10.0pt'><![if !supportEmptyParas]> <![endif]><o:p></o:p></span></font></span></p> > ><p class=MsoNormal><span class=EmailStyle15><font size=2 color=black >face=Arial><span style='font-size:10.0pt'>RUN count_widg in utilities\count_widg.apx ><span style="mso-spacerun: yes"> </span><span style='mso-tab-count:1'> </span>==> >(executable in a procedure)<o:p></o:p></span></font></span></p> > ><p class=MsoNormal><span class=EmailStyle15><font size=2 color=black >face=Arial><span style='font-size:10.0pt'>OR<o:p></o:p></span></font></span></p> > ><p class=MsoNormal><span class=EmailStyle15><font size=2 color=black >face=Arial><span style='font-size:10.0pt'>RUN utilities\count_widg.rex<span >style='mso-tab-count:1'> </span>==> (codelocked >executable file)<o:p></o:p></span></font></span></p> > ><p class=MsoNormal><span class=EmailStyle15><font size=2 color=black >face=Arial><span style='font-size:10.0pt'><![if !supportEmptyParas]> <![endif]><o:p></o:p></span></font></span></p> > ><p class=MsoNormal><span class=EmailStyle15><font size=2 color=black >face=Arial><span style='font-size:10.0pt'>Are there commands that will not run >when codelocked?<o:p></o:p></span></font></span></p> > ><p class=MsoNormal><span class=EmailStyle15><font size=2 color=black >face=Arial><span style='font-size:10.0pt'><![if !supportEmptyParas]> <![endif]><o:p></o:p></span></font></span></p> > ><p class=MsoNormal><span class=EmailStyle15><font size=2 color=black >face=Arial><span style='font-size:10.0pt'>Any comment will be greatly >appreciated.<o:p></o:p></span></font></span></p> > ><p class=MsoNormal><span class=EmailStyle15><font size=2 color=black >face=Arial><span style='font-size:10.0pt'><![if !supportEmptyParas]> <![endif]><o:p></o:p></span></font></span></p> > ><p class=MsoNormal><span class=EmailStyle15><font size=2 color=black >face=Arial><span style='font-size:10.0pt'><![if !supportEmptyParas]> <![endif]><o:p></o:p></span></font></span></p> > ><p class=MsoNormal><!--[if supportFields]><font color=black><span >style='color:black'><span style='mso-element:field-begin'></span><span >style="mso-spacerun: yes"> </span>AUTOTEXTLIST \s "E-mail >Signature" <span style='mso-element:field-separator'></span></span></font><![endif]--><font >size=2 color=black><span style='font-size:10.0pt;color:black'>Javier Valencia, >PE</span></font><font size=2 color=black><span style='font-size:10.0pt; >color:black;mso-color-alt:windowtext'><o:p></o:p></span></font></p> > ><p class=MsoNormal><font size=2 color=black face=Arial><span style='font-size: >10.0pt;color:black'>President</span></font><font size=2 color=black><span >style='font-size:10.0pt;color:black;mso-color-alt:windowtext'><o:p></o:p></ span></font></p> > ><p class=MsoNormal><font size=2 color=black face=Arial><span style='font-size: >10.0pt;color:black'>Valencia Technology Group, L.L.C.</span></font><font >size=2 color=black><span style='font-size:10.0pt;color:black;mso-color-alt: >windowtext'><o:p></o:p></span></font></p> > ><p class=MsoNormal><font size=2 color=black face=Arial><span style='font-size: >10.0pt;color:black'>14315 S. Twilight Ln., Suite #14</span></font><font size=2 >color=black><span style='font-size:10.0pt;color:black;mso-color-alt:windowtext'><o:p></o:p></s pan></font></p> > ><p class=MsoNormal><font size=2 color=black face=Arial><span style='font-size: >10.0pt;color:black'>Olathe, KS<span style="mso-spacerun: yes"> ></span>66062-4571</span></font><font size=2 color=black><span style='font-size: >10.0pt;color:black;mso-color-alt:windowtext'><o:p></o:p></span></font></p> > ><p class=MsoNormal><font size=2 color=black face=Arial><span style='font-size: >10.0pt;color:black'>(913)829-0888</span></font><font size=2 color=black><span >style='font-size:10.0pt;color:black;mso-color-alt:windowtext'><o:p></o:p></ span></font></p> > ><p class=MsoNormal><font size=2 color=black face=Arial><span style='font-size: >10.0pt;color:black'>(913)649-2904 FAX</span></font><font size=2 color=black><span >style='font-size:10.0pt;color:black;mso-color-alt:windowtext'><o:p></o:p></ span></font></p> > ><p class=MsoNormal><!--[if supportFields]><font color=black><span >style='color:black'><span style='mso-element:field-end'></span></span></font><![endif]--><font >color=black><span style='color:black'><![if !supportEmptyParas]> <![endif]></span></font><font >color=black><span style='color:black;mso-color-alt:windowtext'><o:p></o:p></span></font></p> > ></div> > ></body> > ></html> >
================================================ 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/
