#Delete

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Jeff G - 21 May 2008 19:10 GMT

Hello Everyone!
I have been getting “#Delete” in every field between ID 1541 and 1542 in
my Table. I can delete the line by selecting the deleting it, and ACCESS even
asks me if I'm sure I want to delete it. The problem is this; It deletes’,
but when I close the table it comes back (same line). I can’t delete the
information in the fields themselves, nor can I overwrite them.
I did create a new blank database and export the data into it (this I'm
told, is supposed to eliminate corrupt data) I can use the database all day
long and the #Delete's are not there. However, the next morning when I come
in and use the database guess what? It magically appears between the same ID
lines (even the ID line has #Delete in it!!!).
Now my backup database is just fine, but I'm also not using it. It is
strictly for back up. I do my backup on the first of each month, I create a
new blank database and import the data into it and name it Maintenance
Database Backup 01 May 08.MDB etc, etc...
Does anyone have any idea what could be happening?

Signature

Jeff G
Maintenance Tech
Milgard Tempering

Reply to this Message

Jerry Whittle - 21 May 2008 19:25 GMT

Have you run a Compact and Repair?

How about a C&R using the JetComp program?

Instead of exporting to a new database, create a new database file and
import into it.

See what is going on at night time that could cause such a problem.

Signature

Jerry Whittle, Microsoft Access MVP
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.

> Hello Everyone!
> I have been getting “#Delete” in every field between ID 1541 and 1542 in
[quoted text clipped - 12 lines]
> Database Backup 01 May 08.MDB etc, etc...
> Does anyone have any idea what could be happening?

Reply to this Message

Jeff G - 22 May 2008 17:51 GMT

Yes I have run compact and repair. I have no idea what a C&R using the
JetComp program is? But I think I may have solved the problem of it magically
reappearing every night. It seems that our server has been replicating
somehow (there were 9 databases named db1, db2, db3 etc...) and all those
databases were non-corrupt. Not sure why they were being replicated, (suspect
a network problem thru our server which contains the database for sharing)
either way, I'll find out tomorrow morning when I open up the database. We'll
see......

Signature

Jeff G
Maintenance Tech
Milgard Tempering

> Have you run a Compact and Repair?
>
[quoted text clipped - 21 lines]
> > Database Backup 01 May 08.MDB etc, etc...
> > Does anyone have any idea what could be happening?

Reply to this Message