How can I compile the same 4gl program against multiple databases?
On 19th October 1999 batonnet@phase4.com.au (Bryan Tonnet) wrote:- I have a requirement to run 4GL code against multiple databases within the same IDS 7.3 instance. This is a classic set of production, QA and test databases. Basically, I want to use the same 7.2 4GL to compile and run across all these databases (not at the same time) with no changes to the 4GL code, which contains a lot of records LIKE tables and variables LIKE fields. I understand the uses of the DATABASE statement within and outside the MAIN function. Lots of info in here, but it all seemed to assume that the database structures were the same, so that the compile time DATABASE statement would work, and then the dynamic DATABASE statement picks up the runtime database as required from the environment. For me, this won’t work as the schemas of these databases are rarely going to be the same, and it certainly is not guaranteed at any point in time. In any case I have inherited .per files with explicit DATABASE statement
Related Questions
- We would like the N2O Program Locking feature to be enabled in target databases and certain remote databases. What is involved in doing this?
- Can participating library schools offer access to the databases to students and faculty outside the library program?
- Can I use a third party database management program to manipulate the databases?
