We have seperate commercial applications that need to create tables in a common database. Eg: Sales package creates table names beginning with 'SAL', Stock creates table names beginning with 'STK' & so on. Also there can be multiple databases (one each for seperate departments/companies)
We currently create the tables, triggers, indices, etc, with SQL script that is ran from inside IBconsole.
At the moment, it is one script per package, as we sell them a seperate modules, eg: Customer 1 could have Sales & Stock, but Customer 2 only has Stock.
How does everyone else do this ?
The programs are written in Visual C++ & all database access is done using CRecordset classes & SQL statements via EasySoft's ODBC driver, so the script statements could be executed from the client, but is this a wise move ?
It seems silly to hard-code the structures into a .exe
I suspect the way we're doing it now is the right way, but we have concentrated on getting the packages to work, so R&D into the correct method for installing on live systems has had to be left till the end!!!
Thanks in advance
Spencer Window (not a joke name)
spencer.window@eastmidlandcomputers.ltd.uk
We currently create the tables, triggers, indices, etc, with SQL script that is ran from inside IBconsole.
At the moment, it is one script per package, as we sell them a seperate modules, eg: Customer 1 could have Sales & Stock, but Customer 2 only has Stock.
How does everyone else do this ?
The programs are written in Visual C++ & all database access is done using CRecordset classes & SQL statements via EasySoft's ODBC driver, so the script statements could be executed from the client, but is this a wise move ?
It seems silly to hard-code the structures into a .exe
I suspect the way we're doing it now is the right way, but we have concentrated on getting the packages to work, so R&D into the correct method for installing on live systems has had to be left till the end!!!
Thanks in advance
Spencer Window (not a joke name)
spencer.window@eastmidlandcomputers.ltd.uk