Application Version Numbering

Hi,

I have a multiple database application and I am trying to create a single version number strategy.

  1. Each time I update any one of the databases, I want to increment the individual “database version” number using the $TemplateBuild.

  2. Each time something has changed, I want to increment the “Application Version Number”. This might mean that one or many databases have been updated.

I want to hide the fact that there are many databases with individual “database version” numbers. The clients only need to know that they are on the latest “Application Version”.

I do not want to update a database design note in a database that has not been updated, just to update the “Application Version” number, so I am considering that I would have to use a centralised “Release Management Database”, which could hold Release notes, for all clients.

I am going round in cirlces at the moment, trying to think of the best approach. Does any one have a strategy?

Thanks

Paul

Subject: Application Version Numbering

Paul,

Not sure if this is any help but…

I always put the date in the title/file name of all the templates eg if I made some changes to acme.nsf today I would have a template entitled “acme template 2006 11 28” called acme20061128.ntf. If I make a subsequent change on the same day I stick b/c/d etc on the end eg acme template 2006 11 28b.

Using this convention means I always know exactly what version of a database is being used.

Frunobulax