that sounds like a great place to use a stored procedure....
Jeff Watson [EMAIL PROTECTED] Tube Methods, Inc. 610-279-7700 From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of J BLAUSTEIN Sent: Thursday, January 03, 2008 10:57 AM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: storing code in the database Emmitt & Jeff I am beginning to use this procedure for EEPs that do the same task in several forms - did will eliminate the need to open each EEP and make the same modifications - as to the table columns - I am including: Record Number ProgramTilte ProgramColumn Revision date ProgramNotes J At 10:47 AM 1/3/2008, you wrote: 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] <mailto:[email protected]> ] On Behalf Of Emmitt 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 J. Blaustein J Blaustein Associates, Inc 12 Herrick Drive Lawrence, NY 11559 516-371-3445 fax:516-371-4761
