Changing Database Structure After Application Deployment

Hi,
We're planning to rewrite a program of ours from ms-dos with a dbase
database to windows using ado and msaccess or sqlserver 2000. now we have
the problem of database maintenance. because the program is going to be
deployed to multiple customers, we don't want to manually change the
database structure. In dos we had a mechanism with a table which stored the
table definitions, and a table which stored the index definitions. now we
want something similiar to that for windows, and it would be even nicer if
the solution is crossdatabase. it's fine if the "new" database structure(the
structure which the customer doesn't have) is stored in an xml file or
similar.
thanks in advance,
Matthijs ter Woord
if you want to version your databases check out DB Ghost - www.dbghost.com
"M. ter Woord" wrote:

> Hi,
> We're planning to rewrite a program of ours from ms-dos with a dbase
> database to windows using ado and msaccess or sqlserver 2000. now we have
> the problem of database maintenance. because the program is going to be
> deployed to multiple customers, we don't want to manually change the
> database structure. In dos we had a mechanism with a table which stored the
> table definitions, and a table which stored the index definitions. now we
> want something similiar to that for windows, and it would be even nicer if
> the solution is crossdatabase. it's fine if the "new" database structure(the
> structure which the customer doesn't have) is stored in an xml file or
> similar.
>
> thanks in advance,
> Matthijs ter Woord
>
>
|||Can somebody think of a solution which i can build myself?
Matthijs
"mark baekdal" <markbaekdal@.discussions.microsoft.com> schreef in bericht
news:821F7892-552F-4784-9D0A-A3E36D615735@.microsoft.com...
> if you want to version your databases check out DB Ghost -
www.dbghost.com[vbcol=seagreen]
> "M. ter Woord" wrote:
have[vbcol=seagreen]
the[vbcol=seagreen]
we[vbcol=seagreen]
if[vbcol=seagreen]
structure(the[vbcol=seagreen]