support after design - record import and other issues

[Mr.K]

So I finished my database ... then it was time to make it look as if it wasn't an Access DB. I read all the very helpful threads on converting to MDE, hiding access window, starting up my form, placing an icon in my main form title bar so I'm almost set but before I go ahead here is my concern:

So, basically I will make the application look like a stand-alone product and prevent the user from doing anything but using my forms. However, lets say in a month time the user wants to add some feature. Yes, I can keep the original DB and add the feaure on my version but what about all the records that were created in the meantime? How will I be able to import them then, especially if all the tables have autonumbers (which I don't know how to reset to blank in my original) and serve as the linking field for many records? All the relationships between the records would be messed up.
(I'll also have to deal with the security and set it up since one of the tables will store credit card numbers.)

 

[hooks]

It sounds to me like you need to split your database.

Have a front end(your forms) database and a back end(your tables) database. When you need to update or add different things you just add them to the front end and the tables remain the same.

Hope this helps.

Hooks

 

[Mr.K]

I think the changes will not neccessary be limited to one or the other, so I was wondering if there was a different solution. In addition, it is not a network so everything will be sitting on the client's single PC.

 

[Pat Hartman]

Splitting the data from the other objects makes changes easier even if the database is not shared. You can completely replace the user's front end with a new version and his back end, where the data is stored, will not be changed at all.