Emmitt, FYI. If your code is stored in forms, you don't have to re-compile. I change the code in forms all the time and don't need to re-compile. I only re-compile if I change the startup.dat file or Razzak sends out an update.
Jan -----Original Message----- From: "Emmitt Dove" <[EMAIL PROTECTED]> To: [email protected] (RBASE-L Mailing List) Date: Thu, 3 Jan 2008 11:04:26 -0500 Subject: [RBASE-L] - RE: storing code in the database Jeffrey, I want to move all disk-based code into the forms/reports/database so all that is required on disk is a startup file. Yes, we could compile, but as we have to access the app from multiple versions of R:BASE, I want to delay that. Even compiled, I like the ability to change code without having to recompile. Emmitt Dove Manager, DairyPak Business Systems Blue Ridge Paper Products, Inc. [EMAIL PROTECTED] [EMAIL PROTECTED] (203) 643-8022 From:[email protected] [mailto:[EMAIL PROTECTED] On Behalf OfJeffrey M. Watson Sent: Thursday, January 03, 2008 10:47 AM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: storing code in the database Emmitt I would imagine the best way would be to incorporate those on-disk files as stored procedures or if they are only used local to one form, as a form action. But you know your needs best, perhaps you have a reason to want to do it this way? Jeff Watson [EMAIL PROTECTED] Tube Methods, Inc. 610-279-7700 From:[email protected] [mailto:[EMAIL PROTECTED] On Behalf OfEmmitt Dove Sent: Thursday, January 03, 2008 10:43 AM To: RBASE-L Mailing List Subject: [RBASE-L] - storing code in the database Has anyone undertaken a large-scale effort to store code in the database? Not the code in forms or eeps, but command file code that otherwise would reside on disk, and when stored in a table is executed with a RUN SELECT … I’m particularly interested in your table structure to accomplish this. Emmitt Dove Manager, DairyPak Business Systems Blue Ridge Paper Products, Inc. [EMAIL PROTECTED] [EMAIL PROTECTED] (203) 643-8022
