Record is Deleted

[stanton]

Is MSFT Acess so stupid that it cannot overcome this error when trying
to sort/export/edit data?

How the hell one can fix this issue, other then dump the garbage DB.

stanton

 

[Pieter Wijnen]

No, but probably corrupt
Make a copy of the db (to be on the safe side)
Run Tools/Options/Repair & Compact

HTH

Pieter

 

[stanton]

I do have several copies.

There are few rows that is causing this issue and it does not let me
delete this row nor edit. it has an invalid entry in the "autonum"
column and spans through the entire recordset in that row.

Compact works but does not fix this issue. Export fails as soon as it
detect the first invalid row. When I try to even change the table
structure to change autonum to text. it complains that there is not
enough disk space or memory. Yet, I ahve GB of memory and 100GB disk
space.

DB should be flexible enough to fix the rows/tables as Administrator
wishes and not be so restricted.
stanton

 

[stanton]

Listen! - Another test I just did,

This is how GARBAGE is MSFT Access - I'm not sure if their SQL 2005 is
also as garbage and destroy somebody's critical data ove a very STUPID
rows inserted inth database.

I tried to move only one ROW item out of 300,000 rows with a criteria
to another table which has exact definitions. Guess what! this idiot
Access DB complains,

"Record is Deleteld".

Should we fire Microsoft?

Or are they here to defend on their stupidity to put out a garbage
product like that.
stanton

 

[Dirk Goldgar]

I do have several copies.

There are few rows that is causing this issue and it does not let me
delete this row nor edit. it has an invalid entry in the "autonum"
column and spans through the entire recordset in that row.

Compact works but does not fix this issue. Export fails as soon as it
detect the first invalid row. When I try to even change the table
structure to change autonum to text. it complains that there is not
enough disk space or memory. Yet, I ahve GB of memory and 100GB disk
space.

DB should be flexible enough to fix the rows/tables as Administrator
wishes and not be so restricted.

Be sure to let us know if you want help.

 

[John Vinson]

I do have several copies.

There are few rows that is causing this issue and it does not let me
delete this row nor edit. it has an invalid entry in the "autonum"
column and spans through the entire recordset in that row.

Compact works but does not fix this issue. Export fails as soon as it
detect the first invalid row. When I try to even change the table
structure to change autonum to text. it complains that there is not
enough disk space or memory. Yet, I ahve GB of memory and 100GB disk
space.

DB should be flexible enough to fix the rows/tables as Administrator
wishes and not be so restricted.
stanton

This is an unfortunate example of the corruption that JET sometimes
suffers.

My suggestion would be to create a new table, empty, with the same
design (use a Long Integer field in place of the Autonumber if you
wish, or just create another Autonumber).

Base an Append query on the damaged table. Use criteria on the Primary
Key (autonumber) field, but use criteria which can be satisfied *in
the index* without retrieving the damaged records. For instance, if
autonumber values 1365, 1366 and 1367 are known to be bad, use

(fieldname > 1 AND fieldname <= 1364)
OR
fieldname >= 1368

John W. Vinson[MVP]

 

[aaron.kempf]

MDB is a piece of shit.

use Access Data Projects
if you care enough to build a database; then use SQL Server.