I thought the following blog post might be of interest here:

http://sourceitsoftware.blogspot.com/2008/04/database-versioning-part-2.html

It describes how I use dbisam for relatively painless database versioning.

Sean
---------------------------------------
Sean Cross
mailto:sean@sourceitsoftware.com

Pics Print - The photo printing solution for Windows.
http://www.picsprint.com

Rental Property Manager - Rental management made easy
http://www.sourceitsoftware.com

Blog
http://sourceitsoftware.blogspot.com/

Sean,

<< I thought the following blog post might be of interest here:>>

Very nice, thanks very much for the link.

--
Tim Young
Elevate Software
www.elevatesoft.com

Thanks for sharing Sean,
<<the version number is stored (along with a bunch of other info) in an ini
file in the database directory>>
But is there a way to access the ini file when DBISam is used in Client /
Server environments and the database folder is not shared out ?

I use a similar technique as yours but I store the DB version number in one
of the DBISam tables. This technique works on both local and remote
sessions. The limitation is that the table that's storing the version number
cannot be upgraded. Its structure has to remain constant throughout the
different versions.

Regards
--
Gregory Sebastian
EzySoft Developments
http://www.ezysoft-dev.com

"Gregory Sebastian" <gregorys@nospam-ezysoft-dev.com> wrote in message
news:833952AC-1D9C-4D18-B0AD-17E54A8FDE41@news.elevatesoft.com...
>
> I use a similar technique as yours but I store the DB version number in
> one of the DBISam tables. This technique works on both local and remote
> sessions. The limitation is that the table that's storing the version
> number cannot be upgraded. Its structure has to remain constant throughout
> the different versions.
>

Put the database version number in the major (or minor) version of one of
the tables. It does not matter what the table structure is.

Robert

Thanks Rob. I don't know why but for some reason I always thought that those
properties were for DBISam's internal versioning and never used them.

regards
gregory