I have done it two ways, the first is to include a sql text file that I
execute on their database using isql from the install program. The other
method I have used is to have the program check the fields and if they
are not there or are not the correct type, issue a sql command to modify
the database directly. This is done when the database connection is
opened before the tables are opened.

- James

Myles Wakeham wrote:

>We have a vertical market product that we are converting to Firebird. The
>database environment it is being converted from automatically handles
>changes to the schema of the database from version to version, however I
>suspect that we will have to do this ourselves with Firebird.
>
>I would like to know, from other vertical market developers who are using
>Firebird, how they are handling changes in the SQL Schemas when releasing
>updates of their software to their customers? Are there any tools that make
>this process easy to do, or do you have to write this yourself?
>
>Thanks in advance for any advice/assistance.
>
>Regards,
>Myles
>
>===========================
>Myles Wakeham
>Director of Engineering
>Tech Solutions Inc.
>Scottsdale, Arizona USA
>Phone (480) 451-7440
>Web: www.techsol.org
>
>
>
>
>
>
>Yahoo! Groups Links
>
>
>
>
>
>

--
<http://www.harksystems.com> Wireless Communication Solutions


*James Armstrong*
/Staff Engineer/ 2675 Lake Park Drive
N. Charleston, SC 29406
<http://maps.yahoo.com/py/maps.py?Pyt=Tmap&addr=2675+Lake+Park+Drive&csz=N.+Charleston,+SC+29406&country=us>

james@... <mailto:james@...>
http://www.harksystems.com
tel:
fax: (843) 764-1560
(843) 764-3692






[Non-text portions of this message have been removed]