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
Solved

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

Posted on 2013-12-09
4
5,424 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 (Access MVP)
  • 3
4 Comments
 
LVL 57

Accepted Solution

by:
Jim Dettman (Microsoft MVP/ EE MVE) earned 500 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 57
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 47

Author Closing Comment

by:Dale Fye (Access MVP)
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 57
ID: 39706411
That will do it!

Jim.
0

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

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

SQL Server engine let you use a Windows account or a SQL Server account to connect to a SQL Server instance. This can be configured immediatly during the SQL Server installation or after in the Server Authentication section in the Server properties …
As tax season makes its return, so does the increase in cyber crime and tax refund phishing that comes with it
In Microsoft Access, learn the trick to repeating sub-report headings at the top of each page. The problem with sub-reports and headings: Add a dummy group to the sub report using the expression =1: Set the “Repeat Section” property of the dummy…
In Microsoft Access, learn how to use Dlookup and other domain aggregate functions and one method of specifying a string value within a string. Specify the first argument, which is the expression to be returned: Specify the second argument, which …

839 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