Import... which one which way??

[Digital Carnage]

Hi folks,
Okay, I have created a living, breathing, fully operational database
that tracks employees and parking permits. I periodically find "glitches"
that I either overlooked or appeared subsequently due to changes in the
underlying design requested by the end user. So, I take that database and
make a copy of it to which I work on. Then once I've fixed any glitches or
added new features (mostly in forms and reports) I import them over to the
original database and off they go. No data loss, new features to play with
right...? Not exactly. My recent incident involves a form that edits info
on the employee, the form won't display the info but it's definitely there
in the tables. So, I'm wondering which is better... Import tables into
newer database or import forms, queries & reports into older database? Any
recomendations? Thanks

 

[John Vinson]

Any recomendations? Thanks

YES. Use the Database Splitter Wizard under Tools to split the
database into a "frontend", containing all your forms, queries,
reports etc., linked to a "backend" containing only the Tables. Your
table structure *should* be pretty much set at this point; with the
split database you can update a Report or a Query in your copy of the
frontend and simply replace the frontend with a new copy, linking to
the backend. This keeps the data stable.