Linking vs Importing using ODBC connected database

G

Guest

I have established an ODBC connection to a remote database (SQL), via a vpn
connection.

Using this ODBC driver, I have been trying to link tables from this
database. In doing so, the links work OK (the tables are linked, and the
correct fields names, descriptions and numbers of records exist), but all the
record field data displays as #deleted#. Interestingly, using the same ODBC
driver, and IMPORTING the tables (rather than linking) works fine - all the
record fields display the corrent values.

Any ideas?
 
R

Rick Brandt

David said:
I have established an ODBC connection to a remote database (SQL), via
a vpn connection.

Using this ODBC driver, I have been trying to link tables from this
database. In doing so, the links work OK (the tables are linked, and
the correct fields names, descriptions and numbers of records exist),
but all the record field data displays as #deleted#. Interestingly,
using the same ODBC driver, and IMPORTING the tables (rather than
linking) works fine - all the record fields display the corrent
values.

Any ideas?

This can happen if the primary key contains a field with a DataType that doesn't
map directly to an Access DataType (BigInt for example can do this). You would
probably find that a passthrough query also works just fine.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top