missing joins

[Guest]

please, i'm going crazy...anyhow, let me explain...i created a database for
my client. as such, i have a copy of the database here at my office and a
copy at my client's. if an update was needed to my client's database, i used
to be able to write the query/queries and make the form/reports. to get the
changes to my client, i would then create a dummy database and import just
the queries and forms/reports that were new/revised. i would then send that
dummy database by email and they would import the queries/forms/reports
accordingly. and all would be fine.

now, when they import the queries, all the joins are missing and the fields
are messed up, ie.{expr}...

when i think about it now, it's actually a strange thing that it used to
work..that the joins and fields names were maintained in the dummy database
even though the underlying tables weren't in the dummy database and that it
would import maintaining the joins. i liked that feature for sending updates
to my clients.

can anyone help? thanks.
kc

 

[[MVP] S.Clark]

This is a very good reason why it is a good idea to use a split database
architecture. Whenever you update the code, you can overwrite the code mdb,
leaving the data mdb
intact.

 

[Guest]

oh, steve, you're the best!!! thanks so much...i just took a quick peek at
your links/website and realize you've pointed me in the right
direction...there's more for me to learn...much appreciated...thanks again
for your help! i may be in touch!!!!
kacey