Re: 4GL - Database Names

In article <530m37$qud@bamboo.verinet.com>, Cathy Kipp <ckipp@bamboo.verinet.com> writes >Hi Ed, > >There have been lengthy discussions in the past in this group on >how to handle this problem. The consensus is usually: > >(1) For your database statements which appear before your code > > These statements are useful for being able to use the like > syntax when defining variables. These statements are really > only referred to at compile time, and really only require an > empty database with the correct database name and table and > column definitions. At any rate, you should be able to leave > these the way they are. If you want to be able to compile from > live (or somewhere else), just make sure an empty database > (at least) exists there. > Except when in a 4GL module which contains a MAIN function. In that case the executable will connect to the database referenced before your code BEFORE THE FIRST LINE OF CODE IN MAIN IS EXECUTED. >(2) For the code > > You can pass a database name into your program to tell the > program which database you want to use. Then you just need > to use a database statement with an argument (as I think some > of these responses have indicated) to specify which database > you are using. Depending on how your code is written, you may > just need to make a small addition to your main programs and > you'll be done. >Regards, > >Cathy >------------------------------------------------------------------------ >Cathy Kipp E-mail: ckipp@verinet.com >Principal Consultant Fort Collins, Colorado, USA >Database Strategies, Inc. Phone: 1-970-226-0240 >Informix User Group of Colorado - President >International Informix User Group - Board of Directors >------------------------------------------------------------------------ -- David Williams