how do I remove "#deleted" record that keeps reappearing ?

[Guest]

I deleted a record from a table, closed the table and on reopening it found
that the record came up as "#deleted". I deleted all relationships with other
tables and eventaully deleted the other tables. Still #deleted displayed in
all the controls for the allegedly deleted record. Please help!

 

[Guest]

Try doing a Compact and Repair Database from menu TOOLS- Database Utilities.

 

[aaron.kempf]

try using Access Data Projects

Try doing a Compact and Repair Database from menu TOOLS- Database Utilities.

 

[Bill Mosca, MS Access MVP]

Is this a linked table? If it is, what kind of database is it linked to?

You probably could have cleared it by closing Access and re-opening it. But
you shouldn't have to do this at all. Something is keeping your table from
refreshing. Does the table have a unique index on it?

 

[aaron.kempf]

keeping your table from refreshing?

you retard

refresh, re-link; I mean-- MDB is a maintenance nightmare!!!
use Access Data Projcts

-Aaron

 

[Guest]

Thanks for your reply. The table used to be linked but I made sure I deleted
the link via "relationships". So,the table isn't linked and I did not use the
Primary key or any unique index because most of my fields can be duplicated.

 

[Guest]

Thanks for your reply. That sounds drastic but at this point I could try
anything. Besides, I could back up the database before I do it.

 

[aaron.kempf]

always use a simple single-field integer / identity primary key

-Aaron

 

[Bill Mosca, MS Access MVP]

You have misunderstood the term "linked". A linked table is one that i snot
in the database. It is in another database. If the table resides in your
database, the DELETED in the field could well mean that your index on the
table is bad. Remove all indexes on that table and compact the database.
Then create the indexes again. Hopefully, that will fix the problem.

I read your response to Karl. There is nothing drastic about compacting your
database. In fact it should be done routinely.

 

[aaron.kempf]

or; of course-- use Access Data Projects and you won't ever have to
deal with this tedium

I mean seriously.. relink? refresh? re-GET A CLUE, KIDS

-Aaron

 

[Joseph Meehan]

Thanks for your reply. That sounds drastic but at this point I could
try anything. Besides, I could back up the database before I do it.

Drastic??? That is a standard maintenance function.

 

[aaron.kempf]

YES IT IS DRASTIC

Get it through your heads; Access MDB is too complex; and not
reliable-- for the amount of effort that it requires.

Maintenance nightmares; it's just ridiculous.

Use Access Data Projects; and spit on anyone that uses MDB.

-Aaron

 

[Guest]

Oh, I didn't know that. Well, I compacted & repaired it and it looks like the
problem is resolved. Thanks!

 

[Guest]

Thanks Bill. The compact & repair worked! How often should it be done?

 

[aaron.kempf]

never, it is unnecessary.

use SQL Server and Access Data Projects

-Aaron

 

[Bill Mosca, MS Access MVP]

How often to compact really depends on how the database is used. If you are
doing a lot of batch transactions like updates, deletes, inserts and see
that the size of the database file has grown disproportionately, then run
the Compact.

If you don't see much growth, I'd say once a month would probably keep
everything in good shape. But make sure all other users are out of the
database before attempting to compact.

 

[aaron.kempf]

in other words

you can't forecast

you can't prevent

and you can't leave such a flaky-ass solution with real-world
customers.
it's just not practical

-Aaron