"Record Deleted"

  • Thread starter Thread starter Pwyd
  • Start date Start date
P

Pwyd

I'm using a local copy of a database at the moment, however the same problem
occurs with the network copy: Since yesterday, anytime i run a Query that
has any criteria whatsoever it reports "record deleted" and refuses to run.
There are no records deleted. Compacting and repair had no effect. Making a
copy of the query, renaming it, does nothing. However deleting all of the
fields that i'm using with criteria, it works fine. Whats the problem here,
and how do i fix it?
(emergency)
 
Trying creating a new database file, and import all objects from the old file
into the new file. That sometimes knocks it in the head properly.
 
That was going to be my next step -- and thanks for the suggestion.

It has inexplicably (i mean literally during my working with it) decided its
going to work again. I wasn't even fiddling with a new record. It just
decided to work again. Grumble. Is this a network issue of some sort? I
thought records had to be "marked" as deleted before access would report it
as deleted. All of the data was still there, what else would cause access to
report a record as deleted?
 
Nah. I never use floats in calculations of any kind, they're way too
arbitrary. In this case however, we're only dealing with text fields and a
few number/date fields.

It happened after a software upgrade onto the system. I'm just not clear on
why it decided to report they were "deleted" instead of some other error.
 
Pwyd said:
Nah. I never use floats in calculations of any kind, they're way too
arbitrary. In this case however, we're only dealing with text fields and a
few number/date fields.
Click to expand...

ya mean like Dates that are stored internally as a double float number.
( IEEE 64-bit (8-byte) floating-point numbers)
It happened after a software upgrade onto the system. I'm just not clear on
why it decided to report they were "deleted" instead of some other error.
Click to expand...

I don't know either...just that one mechanism might be:

using index to filter query results, but when came time to return all
fields in the query using the index, it could not find that index,
or more than one record met a "no-dup" index. How "software
upgrade" would affect that mechanism -- I don't know.

sorry...

gary
 
I'm sure I can say this better than I did...

A query goes through some parsing steps
as it is run. For a typical non-aggregate Jet query

1) join(s) first

2) then the where clause if exists

3) then the select clause

Indexes are expensive, but they help
our queries zip -- for example you will often see
advice on this newsgroup helping someone
with a slow-running query who has constructed
their Where clause such that Access cannot
take advantage of indexing.

So...where does the "deleted record" message
come from?

Imagine the query has gotten through step 2
using available indexes, but when goes to get
all the fields in the select clause using the index
results, it can no longer find an index. The index
was there back in step 2, but now it isn't?

Access concludes that that record must have
been deleted (say by some other user), even
though that may not be why it cannot find the
indexed record.
 
I understand. Is there a way to rebuild this database to exclude that kind
of indexing, explicitly, like on the options listed for the field?
 
Pwyd said:
I understand. Is there a way to rebuild this database to exclude that kind
of indexing, explicitly, like on the options listed for the field?
Click to expand...

Indexes are defined in table design, but I was just explaining
a "mechanism," not necessarily that "float" is the problem.

It may be that if you go into table design and
delete some index(es), your problem may go away
(if for no other reason than that index was corrupted).

But if this had happened to me, I would first suspect
some type of index corruption and first do exactly
as Steve said -- import into a new db.

Especially if this db had been working w/o problems
for some time.

Recovering from Corruption

http://allenbrowne.com/ser-47.html

Preventing Corruption

http://allenbrowne.com/ser-25.html

The fact that this just happened after
a "software upgrade" would scare me.

What version of Access are you using?

What version of Windows?

Is it a split database?

How many users (each with their own frontend)?

Did you bring backend to "local" computer
only after you noticed this problem?

Had it been working flawlessly for extended time
right up until this "software upgrade?"

What was the "software upgrade?"

Was this a type of software that might have
overwritten Access Jet files?

It wasn't Office 2003 SP3 was it?

Besides Allen's excellent links above, Tony has a

Corrupt Microsoft Access MDBs FAQ here
http://www.granite.ab.ca/access/corruptmdbs.htm

I'm not sure I could further add anything worthwhile
to what is already exhaustively well covered in those links...
 
None of those things. It was an unrelated piece of database software that
uses an entirely different program (sequel worksheet) as its base. Copying
it didn't help at all. Fortunately, it solved itself. It went away again in
2 days, for no reason whatsoever. I'll have to chalk it up to network
connectivity. Still, i'd like to have known what really caused it.
 
Back
Top