Modifying/Add tables to deployed database

[Dave14867]

Hello all,


How do you folks handle modifying and/or adding tables to a deployed database in use by users?

Let's say you add a field to a table that wasn't in the original file, how do you take care of moving the existing data in the original table to a new table without the user having to do anything? Or add a new table and form?

Just trying to think ahead on how to handle updates.

Thanks

Dave

[Homegrownandy]

Users shouldnt have tables held locally. Tables should be back end only and front end issued to users.

[Dave14867]

But what if they have a back end that is local on their system?

[Homegrownandy]

then how will users share data? the back end needs to be "one truth" for everyones use.

Do you all have access to a shared server?

[Dave14867]

It would only be for a specific user or users in a household. Not in a company, so the files would be located on a local machine or server if they had a server set up.

[Homegrownandy]

Idealy you wouldnt be doing updates in this case. But it is possible. best way? I dont know but you need to ensure no data loss.

[Dave14867]

I agree, the only way I can think of is to get the original files back and manually add anything new as far as forms, reports, query's and do a manual update for any affected tables, but that just doesn't seem practical.

That's why I thought I would pose the question on here, someone has to be doing this already.

Thanks

Dave

[ArviLaanemets]

The only practical solution is, you create an update program, which does changes both to front- and back-end, or transfers data from old back-end into new one, and then replaces both front-and back-end files with new ones (user has to determine the location of both at start, when executing). Then you send this updqate program to every user, along with detailed instruction. And then you pray!

[Dave14867]

Arvilannemets,

Can you give me an example of this update program?

Thanks

Dave

[ArviLaanemets]

I know this is doable, but there was never a need for me to do it - all my apps are used in single LAN.

I make changes to back-end in separate location, design a new front-end also there, then I do tests, and when all was OK, I replace back-end with new one, save new front-end to folder where last version of app's front-end is always deployed (every app has version number attached, and every app has his own distribution folder in common parent directory), and remove old front-end to archive folder. After that I send a meil to users (or call them) and inform, that a new version is available, and they can dowload it (only I myself have write right for distribution folder). The system works OK, now almost for 20 years.