I use just two or three columns.. Two Minimum. ColProcedureName TEXT and ColProcedureCode VarChar
The only other columns I have utilized is For Example when the VarChar Column contains NON RBase Code and I need another column to describe what Language is contained.. FWIW, I employ a second table that has a similar structure, but contains a VarBit column instead of Varchar for creation of Files on Disk that are necessary for the application to function (A startup routine does an examination of the needed files and their expected location). I think I have been using RUN SELECT almost as long as it has been available (? since Varchar datatype). And don't forget there is another place to take advantage of this: Form Designer>Table Settings: On my Apayable entry form in the "On Row Entry" I have this in the Edit Box: Select cmdData from intcmd wher cmdname = 'APTrnTot' The RUN command is implied in this location. Handy for sure. ----- Original Message ----- From: "Emmitt Dove" <[EMAIL PROTECTED]> To: "RBASE-L Mailing List" <[email protected]> Sent: Thursday, January 03, 2008 10:43 AM 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 > > > >
