Upgrading amended db schema via Mde

[acgordon]

We have added new columns to a table in our developer db. Now we need to get these columns into the client's system.

Their computer is running on Access runtime, so if we change our existing Access db into a Mde would it be possible to upgrade their database with the changes without corrupting any of the client's data? We're quite happy to overwrite the forms, queries etc. but what happens to the client's data? especially when we have made some changes to the database schema e.g added new columns to the table?

We'd be grateful for any help.

 

[Rabbie]

Do you need to populate the new columns for existing records. What I have done in similar circumstances is first to copy the existing data into a new table. Update the schema for the new table and run update queries as necessary to populate the new fields(columns) that you have added. Then delete the existing table - first removing any relationships it may have. Then rename the new table with the name of of the old table. reinstate the relationships. Repeat for every table as required.

It sounds frightening but if you approach it in an organised way and have plenty of backups it should go through straightforwardly.

It is always a major exercise to add new fields(columns) to existing tables.

The existing FE databases will pick up the new columns when they reconnect the linked tables.

You will need access to the existing BE database with the data to do this.

 

[acgordon]

Yes, client's existing db will need to have data entered into the new columns.

MDE or not, we can do all this copy and renaming on the client's runtime system?