Importing Tables/Missing Relationships

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

We have a template Access Database with all relationships created. Queries
are running off of these relationships. The data is being imported weekly
from other Access and Oracle Databases.

Since upgrading to Office 2003, after importing the tables, the
relationships are missing. It's not all the relationships and it's not the
same relationships every time. This never happened before the upgrade. It
seems to be very random.

We would like to know if anyone knows how to fix this particular error.

The data is being impored from Access 2000, Access 2003 and Oracle 9i
databases.

Thanks in Advance,
Elena
 
I am not sure what you are doing here.
You should define the tables in Access once.
Then create the relationships between them.
Then when you import the data you do not destroy the existing tables you
simply add the data to them.
Are you overwriting the tables?

Just import the data to staging tables and purge the other ones and then
append the data from the staging tables to the real ones.
 
Hello,
I have seen the same problem in my databases. I do not use the
relationships window but instead create the relationships in each query I
write. I imported my queries into a new 2003 database from an old 2000
database and all the Joins were missing from all queries.

Is this like what you saw Elena? I cannot find any information on a problem
like this in the Knowlede Base.

Thanks,
Katy
 
I have more precisely defined this problem. The problem is that if I import
queries from one database to a new database and don't import the supporting
tables at the same time all joins are lost. The field headings become
Expr1:"" where "" is whatever the field heading used to be. This looks like
Access is trying to be smart and updates your queries by deleting the joins
and corrupting the field headings because the tables aren't there. If I later
import the tables (without opening any of the querires) the queries remain
corrupted.

Any advice?
Katy
 
Hi Katy,
The anwser should be pretty obvious - import the tables first and then the
queries.
Access does try to be smart (or helpful.).
In many cases it is very useful - like autosave when you navigate off a
record.
Autojoin behavior has been around since the beginning.
You can disable it under Tools/Options/Tables&Queries tab.
 
Thanks for the help. I did not have this problem in 97 or 2000.

I will disable the feature.
Katy
 
I disabled the feature and got the same results. I tried importing the
tables first and that seems to work. That is inconvenient for me but at
least it is a solution!
Katy
 
Back
Top