Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

#DELETE in all fields of All rows in linked SQL Server table

Posted on 2013-12-09
4
Medium Priority
?
5,553 Views
Last Modified: 2013-12-09
Been migrating some Access data to SQL Server lately.   Experienced a previously unencountered experience this morning.

Opened a table in Access that contained #DELETED in every field and every row of a linked SQL Server table.  Went to SQL Server, and all of the data I imported to the table yesterday is there.  Went back to Access, deleted the linked table, performed a Compact and Repair, closed the database, opened the db, relinked the SQL Server table and still have the same problem.

all of the other tables linked to that SQL Server are working correctly, and the one that is experiencing a problem only has about 2000 records.

Any ideas?
0
Comment
Question by:Dale Fye
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
4 Comments
 
LVL 58

Accepted Solution

by:
Jim Dettman (Microsoft MVP/ EE MVE) earned 2000 total points
ID: 39706226
Dale,

Try adding a TimeStamp column to the table.  As for why, take a look at these two MSKB articles:

PRB: Explaining "Record is deleted" error accessing ODBC table
http://support.microsoft.com/kb/172339

"#Deleted" errors with linked ODBC tables
http://support.microsoft.com/kb/128809

which explains why this occurs and things you can do to avoid the problem.

Jim.
0
 
LVL 58
ID: 39706240
There's also a work around where you can define an index on the Access side if there is no unique index on the SQL side.

Optimizing Microsoft Office Access Applications Linked to SQL Server
http://msdn.microsoft.com/en-us/library/bb188204.aspx

See the section "Adjusting Dynaset Behavior"

Jim.
0
 
LVL 48

Author Closing Comment

by:Dale Fye
ID: 39706341
Jim,

Thanks.  The table already had a unique ID field that was defined as the primary key, and a timestamp field.

However, after reading the references, I went back to the table design and realized that the ID field was a bigint, not an integer.  I believe that was the problem as the new table using int instead of bigint is working properly.

Dale
0
 
LVL 58
ID: 39706411
That will do it!

Jim.
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Preparing an email is something we should all take special care with – especially when the email is for somebody you may not know very well. The pressures of everyday working life stacked with a hectic office environment can make this a real challen…
If you need a simple but flexible process for maintaining an audit trail of who created, edited, or deleted data from a table, or multiple tables, and you can do all of your work from within a form, this simple Audit Log will work for you.
Do you want to know how to make a graph with Microsoft Access? First, create a query with the data for the chart. Then make a blank form and add a chart control. This video also shows how to change what data is displayed on the graph as well as form…
This lesson discusses how to use a Mainform + Subforms in Microsoft Access to find and enter data for payments on orders. The sample data comes from a custom shop that builds and sells movable storage structures that are delivered to your property. …

636 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question