Version Number for a DBC

[Larry Oliver]

Has anyone got any ideas for creating a version number for a dbc by adding a
user field or other method. I want a way that I can keep seperate version
number for the dbc similiar to that of the EXE version. We have a
commercial application that we provide for a client base providing upgrades
and enhancements. We have an automated way to update there systems (not all
clients get the upgrade at the same time) but the way to we update the DBC
is by changing the Major version of the EXE. From time to time we have a
need to update the DBC only and have no way to do that as well as it is
quite confusing trying to keep track of several different versions of the
DBC with no real easy way to differentiate them.

Thanks for any ideas.
Larry

[Sietse Wijnker]

Hi Larry,

To accomplish the version numbering, you can do a couple of things:
1. Create a text file in the same folder as your DBC containing the version
2. Create a separate table containing a record which holds the version
number
3. Use DBGETPROP() and DBSETPROP(). The problem here is the most obvious
db-property would be 'Version', but that's read-only. Therefore the only
DB-property that's usable would be the comment property.

I'm sure there are some more solutions to the problem, but these are the
most simple to understand an maintain.
If i was to choose, i'd go for the DB-comment property. You could even go
with the comment property for the tables so you'll have some kind of
versioning for them.

HTH,
Sietse Wijnker

Post by Larry Oliver
Has anyone got any ideas for creating a version number for a dbc by adding
a user field or other method. I want a way that I can keep seperate
version number for the dbc similiar to that of the EXE version. We have a
commercial application that we provide for a client base providing
upgrades and enhancements. We have an automated way to update there
systems (not all clients get the upgrade at the same time) but the way to
we update the DBC is by changing the Major version of the EXE. From time
to time we have a need to update the DBC only and have no way to do that
as well as it is quite confusing trying to keep track of several different
versions of the DBC with no real easy way to differentiate them.
Thanks for any ideas.
Larry

[Rick Bean]

Larry,
It's trivial if you use Stonefield Database Toolkit, just add a new user field to the metadata. SDT has a whole host of advantages for anyone using VFP native tables.
(http://www.stonefield.com/)

Rick

Post by Larry Oliver
Has anyone got any ideas for creating a version number for a dbc by adding a
user field or other method. I want a way that I can keep seperate version
number for the dbc similiar to that of the EXE version. We have a
commercial application that we provide for a client base providing upgrades
and enhancements. We have an automated way to update there systems (not all
clients get the upgrade at the same time) but the way to we update the DBC
is by changing the Major version of the EXE. From time to time we have a
need to update the DBC only and have no way to do that as well as it is
quite confusing trying to keep track of several different versions of the
DBC with no real easy way to differentiate them.
Thanks for any ideas.
Larry

[R D Black]

Larry,

I update four different DBC. What I did was track what update I have run
against which dbc. I use it to add tables and make field corrections like
size and data types.

I created a separate application to make these changes. I store which
updates have been run against which dbc. The application tracks the location
of the dbc the version and if the last update was a success. If the update
is not a success the program emails me and lets me know which version failed
and what the error was.

Let me know if you would like more info.

R D Black

Post by Larry Oliver
Has anyone got any ideas for creating a version number for a dbc by adding a
user field or other method. I want a way that I can keep seperate version
number for the dbc similiar to that of the EXE version. We have a
commercial application that we provide for a client base providing upgrades
and enhancements. We have an automated way to update there systems (not all
clients get the upgrade at the same time) but the way to we update the DBC
is by changing the Major version of the EXE. From time to time we have a
need to update the DBC only and have no way to do that as well as it is
quite confusing trying to keep track of several different versions of the
DBC with no real easy way to differentiate them.
Thanks for any ideas.
Larry

[Demetrios Panayotakopoulos]

Hi Larry,

I do not think that you can do it the way you are thinking. It would be nice
if yould right click/properties and get the version number.

I always include a table in dbc with various info including the database
version.
When I deliver a new exe this checks if the database is in correct version
and if not makes the proper modifications and updates the database version
number.

Demetrios, Greece

Post by Larry Oliver
Has anyone got any ideas for creating a version number for a dbc by adding a
user field or other method. I want a way that I can keep seperate version
number for the dbc similiar to that of the EXE version. We have a
commercial application that we provide for a client base providing upgrades
and enhancements. We have an automated way to update there systems (not all
clients get the upgrade at the same time) but the way to we update the DBC
is by changing the Major version of the EXE. From time to time we have a
need to update the DBC only and have no way to do that as well as it is
quite confusing trying to keep track of several different versions of the
DBC with no real easy way to differentiate them.
Thanks for any ideas.
Larry

[Paul Pedersen]

I have done this using a stored procedure that returns the database version.
When I change the version, I change the stored procedure.

Post by Larry Oliver
Has anyone got any ideas for creating a version number for a dbc by adding
a user field or other method. I want a way that I can keep seperate
version number for the dbc similiar to that of the EXE version. We have a
commercial application that we provide for a client base providing
upgrades and enhancements. We have an automated way to update there
systems (not all clients get the upgrade at the same time) but the way to
we update the DBC is by changing the Major version of the EXE. From time
to time we have a need to update the DBC only and have no way to do that
as well as it is quite confusing trying to keep track of several different
versions of the DBC with no real easy way to differentiate them.
Thanks for any ideas.
Larry

[Michael]

I've also accomplished this with Stonefield Database Toolkit
(www.stonefield.come) which allows you to add properties, like a database
version to the DBC. Nice part about this is it can also be used to recognize
when structural updates are required and can be checked by your app when
loading. Sounds like an ad, but I could not live without SDT.

Post by Paul Pedersen
I have done this using a stored procedure that returns the database
version. When I change the version, I change the stored procedure.

Post by Larry Oliver
Has anyone got any ideas for creating a version number for a dbc by
adding a user field or other method. I want a way that I can keep
seperate version number for the dbc similiar to that of the EXE version.
We have a commercial application that we provide for a client base
providing upgrades and enhancements. We have an automated way to update
there systems (not all clients get the upgrade at the same time) but the
way to we update the DBC is by changing the Major version of the EXE.
From time to time we have a need to update the DBC only and have no way
to do that as well as it is quite confusing trying to keep track of
several different versions of the DBC with no real easy way to
differentiate them.
Thanks for any ideas.
Larry