By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,694 Members | 2,121 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,694 IT Pros & Developers. It's quick & easy.

WARNING: Relationships not imported with data

P: n/a
A while back I imported tables to a new database via Files-->Get
External Data --> Import...

All was well for several months, and then the database started behaving
badly in a couple of ways, including slow (actually speed was fine when
users opened database, then deteriorated after a few minutes of normal
use) and errors when trying to enter data. Specifically, this appears
when entering data in a subform, even when an individual is the only
one on the system: The Microsoft Jet database engine stopped the
process because you and another user are attempting to change the same
data at the same time. (Error 3197) Then #ERROR appears in the fields,
but after going to another record and coming back, the data is in
place.

In poking around, I realized that there were no relationships set on
the data. After hours and hours of mucking around and trying to
recreate past operations, I found what is likely the sticking point.

The data table had a linked table which no longer had a valid path.
I'd ignored the "<Path> is not a valid path. Make sure that the path
name is spelled correctly and that you are connected to the server on
which the file resides" message since that table was obsolete.
HOWEVER, I now realize that this dud table apparently caused the loss
of all relationships. If I recreate the situation but without
selecting the dud table, all is fine. FWIW, I should mention that I was
importing to a newer version of Access.

So from now on I'll assume things went badly if I see any kind of error
message while importing. And if I remember to be meticulous I'll look
for relationships after I import data. (But what else should I check
for? Indexes? Other table properties? Who knows.)

And I wonder if the problem amounts to more than just missing indexes.
Not that I expect to ever know.

P. Emigh

Dec 2 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
when you are importing tables theres an advanced button which opens an
area with a check box for importing relationships...

spilt milk!

you are going to have to take a copy of the database and work on fixing
the data offline. sounds like more than referential integrity though,
you could have corrupted data. decompile, compact and repair and
manually fix referential integrity. depending on the size of the
database you are working with this could take time... use unmatched
query wizard to help identify orphans and hook them up or delete them.
then rebuild relationships.

Dec 2 '05 #2

P: n/a
Importing relationships was selected, and I've confirmed by recreating
the situation that they fail to import in the situation I described --
fer real!

Good advice -- you more or less described my plan. I got their data at
the end of the word day on Friday, and I'm about ready to dig in on
reconstructing their data. Wish me luck, because if I don't have them
up and running at 7:15 am on Monday, my name is mud.

Phyllis
BillCo wrote:
when you are importing tables theres an advanced button which opens an
area with a check box for importing relationships...

spilt milk!

you are going to have to take a copy of the database and work on fixing
the data offline. sounds like more than referential integrity though,
you could have corrupted data. decompile, compact and repair and
manually fix referential integrity. depending on the size of the
database you are working with this could take time... use unmatched
query wizard to help identify orphans and hook them up or delete them.
then rebuild relationships.


Dec 3 '05 #3

P: n/a
How'd it go?

Dec 5 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.