#DELETED everywhere

[Guest]

I linked a table via ODBC (to MS-SQL 2000 database) and when I open the table
I get "#Deleted" in every field on every record (all 30 by 3566179 of them!).

What should I be looking for? Other links to the same database (different
tables) work fine - just not this one (actually, I've found 4 that have
similar behavior).

HELP, Please...

 

[John Vinson]

I linked a table via ODBC (to MS-SQL 2000 database) and when I open the table
I get "#Deleted" in every field on every record (all 30 by 3566179 of them!).

What should I be looking for? Other links to the same database (different
tables) work fine - just not this one (actually, I've found 4 that have
similar behavior).

HELP, Please...

Try using Tools... Utilities... Linked Table Manager to relink to
these tables. Sometimes the linkages get messed up and the relinking
can repair them.

John W. Vinson[MVP]

 

[Guest]

Thanks, but I already tried that - no luck.

Other research indicated a possible problem with MS-SQL 2000 field type
BIGINT (which I'm using as an IDENTITY primary key field). Even after I
converted the field to DECIMAL(12,0) and re-linked I got the same trouble.

Any other ideas?

 

[Guest]

Results of recent experiments:

In researching this problem, I read (somewhere) that Access doesn't work
well with key fields of type BIGINT. My first attempts to fix this didn't
work (converting to DECIMAL(12,0)), presumably since Access still can't
handle the large integer value as a key field (my tests showed that Access
got correct BIGINT values when they are NOT key fields, but I was not
exhaustive in checking this).

Anyway, now the problem is very specific: How do I get Access to work with
ODBC linked tables to MS-SQL 2000 Server where the tables have BIGINT primary
key fields?

Would "pass-through" queries do the trick? If so, what are they and how
would I use them?

TIA!

-Stevel