Rbase momenclature and codelock issues

[Javier Valencia]

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