Record is Deleted

[Lhuffst]

My tables were in a 97 version. When I created a new 2003 version and imported all of the tables, it keeps telling me that record was delete for one table. I thought it might be corrupted so I tried to fix it but you can't because it's an earlier version. It will not let me import the records in access or excel. What can I do to get this table to convert to the 2003 version?
lhuffst

 

[Remou]

Have you tried exporting from '97 to a CSV?

 

[Lhuffst]

Yes. I have also just tried to compact the table with access 97 and it didnt' give me any errors but when I import that table to the new 2003 version, it says record deleted.

I looked at the conversion error file that was just created and it says
1017-Could not find field description

The table with the field names does exist. Any suggestions?
lhuffst

 

[Remou]

If you can export to a CSV, can you not import from the CSV, or have I missed your point?

 

[Lhuffst]

Hi. I have finally been able to export to a csv mode. Apparently there was some problem with the autonumber field on the table. At this point I now have a 2003 front end and back end but still have my original problem. When I update a record and try to save it, I get a write conflict error. I've changed the recordlocks property to edited record as suggested but still have the same problem. Do you know how I would resolve this issue? It almost looks like the record lock is not releasing when people have exited the system.

The odd thing is that until some of our pc's were upgraded to Office servic Pack 3, this problem didn't exist. Now I can't seem to get around it.

Thanks - you are always a big help
Lhuffst

 

[Remou]

There is a know problem with sp3.

Try this first:

http://support.microsoft.com/default.aspx/kb/945674

 

[Lhuffst]

Hi Remou,

I copied the db from the share drive to my local drive. Installed the patch, rebooted but am still getting the same write conflict message.

Any other ideas?

I'm going to reopen the database and do another compact & repair just in case. Question... If I open the front end and do the compact/repair, does it automatically do the back end if I have the tables linked? Both are access2003
Lhuffst

 

[Remou]

No, you must compact and repair both the back and front-end. Can you import the problem table into a new, blank database?

 

[Lhuffst]

I imported the tables to a new database and still have the same results. Is there a way to check and see if a record is in an open state?

 

[Remou]

Are all the tables giving problems or only one? Have you checked for an ldb after everyone has exited? Does every one who uses the system have full permissions on the back-end? Has each user their own front-end?

 

[Lhuffst]

The person who set this up used a workgroup which has admins, my name and the original programmer.

If I start the front end up with a workgroup file and the fe is linked to the be, will the security translate to both or do I need to do something to the backend as well?

I will modify the workgroup. I never thought to look there since the database has been fine for several years. the only thing that has changed recently is the sp3 update that was applied to some of our pc's and not all.

 

[Remou]

Sorry, I was not clear, I meant permissions as in folder permissions, not workgroup permissions.

The ldb file should tell you if there are any locks.

 

[Lhuffst]

I've been looking for the ldb file and do not see it on my local pc. However, I also have to choose cancel to the prompt about copying from the clipboard so I suspect the minute I do that, I lose the ldb file. Tomorrow's another day

 

[Remou]

Look for an ldb in the directory that contains the back-end. See you tomorrow.