Importing tables into runtime database 1

[jac123]

Maybe someone can point me in the right direction. I have a standalone DB that I created from Access 2003, and plan to convert this into a runtime program.
If the user installs the program and inputs information into the DB for some time, then purchases a new computer and installs the program once again, there needs to be a way for them to import, either the old tables or the data from the old tables. I’m not sure which or how this is accomplished.
I tried using Import, but it creates a new table (example: if I have a table: Recipes, it created a table called Recipes1).
I’ve looked at linking, merging etc. but not sure I’m heading up the right path. If anyone out there has some insight on the subject, I would be very interested in hearing from them.
Thank you very much.

 

[Remou]

You could consider a split database with your application as the front-end and the tables as the back-end. that way, the user can simply copy the tables across in the same way as any other data. Alternatively, you could create an import module that renames or deletes the 'old' tables and then imports, this could be quite unsafe, depending on the users, and you would probably need an 'undo'.