[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 223
  • Last Modified:

Access 2007 - Linked DB table problem

Every time I open a linked DB Table, the top thre rows contain the term  #Deleted
This term appears in every cell of the top three rows. When I delete the three top rows, and  reopen the table, #Deleted appears again.
What do you think could be the problem?
0
sebastiano72
Asked:
sebastiano72
  • 7
  • 5
  • 2
  • +1
1 Solution
 
mbizupCommented:
Are you opening the table while a form that has affected that data is still open?

Close all forms and other objects before opening the table so that you are opening that table alone.  

Does that make a difference?
0
 
mbizupCommented:
If not, try running Compact & Repair on the linked (Back End) database.
0
 
sebastiano72Author Commented:
I have not forms in this database, for the moment only the linked DB table. I delete the three top lines directly from the linked table
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
plummetCommented:
Hi,

What are you linking to, Access, SQL server, etc?
0
 
sebastiano72Author Commented:
Not sure, but the table I am linked to ends in .DBF
0
 
mbizupCommented:
<<  I delete the three top lines directly from the linked table >>

If you are deleting the data directly from the Back-End, you may need to refresh the links or at least close and reopen the table for that data change to be seen in the front-end.
0
 
mbizupCommented:
Not sure about DBF, but I just tested this with an Access Back-end.

If I delete rows from a table in the back-end file while  it's linked table is open in the front-end, I see #deleted# rows in the linked front-end table.

Closing and reopening the linked table in the front-end updates the display so that the #deleted# rows no longer show up (this doesn't happen automatically if the linked table is open).
0
 
sebastiano72Author Commented:
I do not have software to open .DBF Table. I can open it only as a linked table to Access, therefore cannot operate on the back end unless via Access.
Once Linked i to Access, Imanage to delete rows from the table, this is fine, but when I delete the rows where all che cells contain #Deleted, these rows reappear upo reopening the linked table.

If I run a query on this table, Ie first column which contains the YEAR in text format (4 characters),  the query seems to work and displays data, but after a few seconds I get a message box which says"The search Key was not found in any record!, and then all of the cells in the query read #Name?
0
 
plummetCommented:
DBF tables are dBase - or xBase. From what I remember records in dbase files are not removed until the files are "packed" but I would expect it to show the deleted record rather than #Deleted.

Are the records below these three all OK? I know I have had problems in the past where Access is having trouble recognising a linked 'memo' type field. When it hits a record it doesn't like then you may well see the #Name error.

There are some settings for the XBase engine in the registry - are you familiar with working with the registry? You are looking for the Engines folder under which should be an XBase folder which contains settings which include "Deleted". However the setting for Deleted is Off by default, which is as you'd expect...but this is worth investigating. And also, is there a .INF file in the folder with the DBF file(s)?
0
 
sebastiano72Author Commented:
Thanks for letting me know about dBase files.

The records below the three are OK

I am not familiar with XBase engine registry or with the workings of the registry

There are no .INF files but there are .MDX and SQL Server Replication Snapshot Script
0
 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:
This most likely doesn't pertain per say because your probably using an ISAM driver rather then a ODBC one, but the article below does give you insight on how JET works with linked tables.


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

<<If I run a query on this table, Ie first column which contains the YEAR in text format (4 characters),  the query seems to work and displays data, but after a few seconds I get a message box which says"The search Key was not found in any record!, and then all of the cells in the query read #Name? >>

  That to me seems significant.  Sounds like Access is having problems keeping track of records and when it goes to fetch them again, cannot find them.  Adding an index may help.

  Also, as plumment mentioned, there are settings in the registry to control the initialization of the ISAM drvier for Dbase:

This is the 2007 settings from MSDN:

Initializing the dBASE Database Driver
http://msdn.microsoft.com/en-us/library/bb177605(v=office.12).aspx

And 2003 from Office Development, which may have a little more info.

Initializing the dBASE Database Driver
http://office.microsoft.com/en-us/access-help/initializing-the-dbase-database-driver-HP001032158.aspx

 I would try playing with the Deleted setting as has been said and also the Exact setting, which changes how string compairs are done.

Jim.
0
 
sebastiano72Author Commented:
no
0
 
mbizupCommented:
<no>

??

You accepted my answer as a solution.

If this is not resolved, please let us know.
0
 
sebastiano72Author Commented:
I solved the problem by running the file through a DBF recovery tool. THe problem is now fixed.
Thanks for your help
0
 
sebastiano72Author Commented:
DBF file was currupt, and solved problem wiht DBF recovery tool
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 7
  • 5
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now