MS Access showing #deleted in a table linked to SQl server

Hi all

doing my head in showing #deleted in all records for a linked table to a SQL 2000 back end using odbc. Other tables using the ODBC are fine

can anyone help!!

Davoman
LVL 1
davomanAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

ahmedbahgatCommented:
possibly this may help

http://support.microsoft.com/default.aspx?scid=kb;en-us;264766

http://support.microsoft.com/default.aspx?scid=kb;en-us;323201 

also i found that if the sql table name has the following togther, the problem you have may happen:

1, the table name has spaces
2, the field name have spaces
3, there plenty of records and fields in the table

the above can be tackled by removing the spaces from fiels names and the table name

cheers



0
davomanAuthor Commented:
None of these seem to help.

To elaborate, '#Deleted' appears in all records when viewing the table through Access. This has worked before, but after moving the database to a new server the problem occured. It also only seems to happen to this table - there are several other linked tables that all work perfectly.
0
coffeeshopCommented:
Has the primary key of the table changed, or didn't it appear not unique for any reason in Access? Try to read the records through a query with the property "Snapshot" instead of "Dynaset". If you can see the records correct, it may a problem with the key or non-unique entries in the table. Another possible reason is a problem with your local odbc-driver, if the server changed to another version.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

davomanAuthor Commented:
Thanks for the suggestions but we found the solution in the end.

In case anyone else runs across this problem, the reason was that a field type had been changed to bigint in SQL, and Access doesn't seem to support numbers of that size. Changing the field type back to int solved it (and it was just coincidence that it all happened when we moved servers - it was the first time the linked tables had been refreshed since the change)
0
moduloCommented:
PAQed with points refunded (500)

modulo
Community Support Moderator
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
SambaCorCommented:
I have exactly the same problem but I don't have any BigInt data type on any of my primary keys.
Any suggestion?

Sun
0
Steve BinkCommented:
SambaCor,

This question has been closed for about 3 years.  You would do better to post a new question in the appropriate zones.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.