Access Front End Update

[AccessNut]

I have a split database, and I'm trying to figure out the best way to update the front end for my users. Some of my users will have their own queries, reports, etc., that they have built themselves into their local copy of the front end. When I upgrade the front end, I do not want to wipe out their work, nor do I want them to have to import these queries/reports every time they get an updated version of the front end.

I'm thinking about adding an "Import" button in the new front end, so when a new front end is deployed, the user can click on this button, which will ask them where their old front end is, then compare the old front end with the new front end, and then automatically import anything that is in the old front end but is not in the new front end. All these (hopefully) can be done in VB code.

Has anyone tried this approach? Will it work? Any potential pitfalls? Thanks in advance.

 

[KenHigg]

I would never let a user add stuff to a production db. Instead give them an empty .mdb with read only links to the data and then they can create what ever they like.

Just my opinion

 

[HiTechCoach]

I totally agree. I only deploy a front end as an MDE.

For custom queries, I have a form that the allows the user to create there queries and then store the SQL statement in a table in the back end.