Don't forget that you can codelock individual (little) files, so if you want to make changes to the code, just change the ASCII file, re-codelock it and you are good to go,. The advantage is that it protects "proprietary" code and prevents users for messing with the code; if you have users that do not attempt to "look" at the code, you are lucky, I have users that have changed the code in ASCII files and created big problems, because most of the time they will not even admit doing it, some users have even attempted to open the .RB* files with programs such as word processors, spreadsheets and even AutoCAD (true case). Knowing that the files are codelocked, and thus not viewable, has in most cases stopped this problem. During development and testing I use ASCII files, once the system is pretty well debugged, I codelock the files individually. If I need to upgrade the code later, I can always e-mail the user the codelocked version of the updated command file which they can drop it in the proper directory and that is all it takes. Just my 2 cents.
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] Behalf Of Bernard Lis Sent: Sunday, March 02, 2003 3:57 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Trace/Crashing - Razzak's Reply Amen, David Bernie Lis ----- Original Message ----- From: "David M. Blocker" <[EMAIL PROTECTED]> To: "RBASE-L Mailing List" <[EMAIL PROTECTED]> Sent: Saturday, February 22, 2003 3:33 PM Subject: [RBASE-L] - Re: Trace/Crashing - Razzak's Reply > Dan > > My two cents worth. > > The problems you are experiencing here only reinforce my long standing > belief that though maintaining lots and lots of little ASCII files is a > challenge, it is still prefererable to the many hassles of dealing with > codelocked files!! > > David Blocker > > ----- Original Message ----- > From: "Dan Champion" <[EMAIL PROTECTED]> > To: "RBASE-L Mailing List" <[EMAIL PROTECTED]> > Sent: Friday, February 21, 2003 1:22 PM > Subject: [RBASE-L] - Re: Trace/Crashing - Razzak's Reply > > > > > > Dennis, > > I agree, I would have liked them to have used the standard quoting ', > > however there are at least 600 programs (including eeps) Reports with > > variables, forms with variables that use the double quotes. > > I do have the main menu program (the running program that calls the > form > > that calls this particular form that disconnects from the DB, sets the > > quotes "", then reconnects, then disconnects and stays disconnected > > between every menu choice. So the quotes are set and reset by every user > > all day long. (had to to this a couple of years ago to resolve quote > issues.) > > I wish I had the time available to edit every program and use standard > > quoting, however it isn't feasible. > > In short, the set quotes = " "" " command was issued just previous to > > calling this apx. > > > > Javier..... I think you hit a nail on the head.... my ASCII file I didn't > > name .app, but .eep so it woulnd't get erased when I delete the .apx > > from Rbase. I will rename it to .app and see if that lets me step > through it. > > > > > > Dan > > > > At 08:30 AM 2/21/03 -0800, you wrote: > > > > >Dan, > > > > > > > $COMMAND > > > > inform2 > > > > SET ERROR MESSAGES OFF > > > > CLEAR V i* > > > > SET V imessage = + > > > > "You may search based on any known information. Just click + > > > > on the field you do have information about and fill it in. Then hit > > > > enter. + > > > > You only need to fill in one field" > > > > > >You are using non-standard quotes. Codelock assumes the single quote. > > > > > >You have two options: > > > > > >1. Put SET QUOTES="""" at the top of the first command block of every > > >command file: > > > > > >$COMMAND > > >inform2 > > >SET QUOTES="""" > > >SET ERROR MESSAGES OFF > > > > > >2. Go throught the work to convert to single quotes. It is worth the > > >trip, but time consuming. > > > > > >Dennis McGrath > > > > > > > > Dan Champion > > P.O. Box 223 > > Grandville, MI. 49428-0223 > > www.championsolutions.net > > > >
