H
HGBenson
how can I stop Access from converting linked tables to local tables during
the conversion process
the conversion process
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
D
Douglas J. Steele
I've never heard of Access doing this!
I suppose it's possible that it's noticing that your backend tables are in
Access 2003, and it knows that Access 97 won't be able to read them, but I
didn't think that was part of Access 2003!
See whether converting the back-end to Access 97 first makes a difference.
I suppose it's possible that it's noticing that your backend tables are in
Access 2003, and it knows that Access 97 won't be able to read them, but I
didn't think that was part of Access 2003!
See whether converting the back-end to Access 97 first makes a difference.
H
Harry Benson
The backend tables are already in access 97, but they get embeddedd in the
coverted database.
coverted database.
R
Rick Brandt
Douglas said:I've never heard of Access doing this!
I suppose it's possible that it's noticing that your backend tables
are in Access 2003, and it knows that Access 97 won't be able to read
them, but I didn't think that was part of Access 2003!
See whether converting the back-end to Access 97 first makes a
difference.
I have. When I was strugling with a file "problem" the other day I recalled
someone saying that they had fixed a file by converting to a newer version
and then back again so I gave it a shot. Converted to2002/2003 format
(using 2003) and then back again. Everything went great except I noticed
that many (not all) of my linked tables were now local. I don't know if it
was the convert up or the convert down that did it, but I had been assuming
that it was the convert down.