Updating MSAccess DBs between Versions
-
I am working with C++ and MSAccess trough ODBC and I have a ligistics nightmare when it comes to releasing new versions of my databases. Right now, If I make a change to my database structure I have to write a little patch program that will add, remove, or edit columns or tables in the database and these things are hardcoded and can only work for specific versions. I was wondering if anyone knows of any utility programs that will let me make the changes over multiple versions. Basically, if the user has version 1.0 and wants to upgrade to 3.0 the utility will then change the existing database appropriatly. Or a user wants to go from 2.0 to 3.0 and so forth. So a utility that will let me store what needs to changed in the database from version to version, and make these changes on upgrade. That way, the users don't lose any data and the program won't crash from trying to access a column that was not in the older versions. Thanks in advance,:-D *********************** Tony Fontenot Recreational Solutions tony@recsolutions.com ***********************
-
I am working with C++ and MSAccess trough ODBC and I have a ligistics nightmare when it comes to releasing new versions of my databases. Right now, If I make a change to my database structure I have to write a little patch program that will add, remove, or edit columns or tables in the database and these things are hardcoded and can only work for specific versions. I was wondering if anyone knows of any utility programs that will let me make the changes over multiple versions. Basically, if the user has version 1.0 and wants to upgrade to 3.0 the utility will then change the existing database appropriatly. Or a user wants to go from 2.0 to 3.0 and so forth. So a utility that will let me store what needs to changed in the database from version to version, and make these changes on upgrade. That way, the users don't lose any data and the program won't crash from trying to access a column that was not in the older versions. Thanks in advance,:-D *********************** Tony Fontenot Recreational Solutions tony@recsolutions.com ***********************
Don't know if this helps but thier is a undocumented access command switch /decomplie. It will upgrade or change the database to your version of visual basic. Needless to say use with extreme caution. MSACCESS.EXE /decompile c:\somename.mdb For a utily to handle different versions You might want to try MS Project.
-
I am working with C++ and MSAccess trough ODBC and I have a ligistics nightmare when it comes to releasing new versions of my databases. Right now, If I make a change to my database structure I have to write a little patch program that will add, remove, or edit columns or tables in the database and these things are hardcoded and can only work for specific versions. I was wondering if anyone knows of any utility programs that will let me make the changes over multiple versions. Basically, if the user has version 1.0 and wants to upgrade to 3.0 the utility will then change the existing database appropriatly. Or a user wants to go from 2.0 to 3.0 and so forth. So a utility that will let me store what needs to changed in the database from version to version, and make these changes on upgrade. That way, the users don't lose any data and the program won't crash from trying to access a column that was not in the older versions. Thanks in advance,:-D *********************** Tony Fontenot Recreational Solutions tony@recsolutions.com ***********************
I don't know of any utility that does this, but the problem is the same with any database tool you happen to be using. What I have done in the past is to write a conversion utility to convert from V1 to V1.5, V1.5 to V2, etc. Instead of updating the database they are using you might consider moving their data into a new database instead. What I do is if they are installing Version 3.0 over version 1.0, I do 2 conversions. First I move their data from 1.0 to 2.0. And then I move the converted 2.0 database to 3.0. Pain in the but, but I only have to deal with the 2 most current versions at any given time.