Maintaining Relationships

[Don]

I'm developing an application and will need to release new
copies of the program on a regular basis. The user will
be updating data (and is far away). I need a way to put
together their data and my changed programs in one
database so they can get updates without losing their data.

I'm using relationships, and can find no way to program
them in.

I'm using Autonumbering in some fields, so I need to keep
the existing numbers.

Any thoughts?

 

[tina]

have you thought about using a split database - tables and
relationships in a "backend" file and all other objects in
a "frontend" file? you can release new versions of the
frontend without touching the backend where the user's
data resides.

 

[Don]

No, I hadn't. Works great. Thanks for the idea!