Suddenly there is: Recordset not updateable

[Guest]

My db contains a little over 6500 profiles/contacts with many, many events
linked to the contacts.. When exiting the 'contact edit form' of a existing
contacts I rcvd the message that someone else made changes (that was me as
I'm the sole user- I think I know how it happened - edited from two different
input screens without saving/refreshing in between) and I chose the "save the
edits" option. Oops, bad move. The record I was editing was deleted which
left some deadended links. I re-entered the contact record and updated the
links to the new autonumber directly in the be tables.

Now when I try and edit using the form I've been using for over a year, I
get the "record set not updatable" error.

If I replace the be with the backup be from yesterday, the error (using the
same fe) doesn't occurr (of course today's data entry isn't there).

The problem seems to be in the be but I have no clue where to start. Any
suggestions?

There are two tables behind the form and if I delete one, the error goes
away. But the same two tables in the backup be work well.

Thanks for any words of help,
Jael

 

[Guest]

Well I found part of the problem but ...
I opened the be database and began making backups of each table (copies).
The main (largest) table would not copy "Assigning a null value to a non
variant field".
Looking at the table, I found one autonumber (Id) missing and the data in
the fields for that record corrupt. I deleted it and the table copied fine,
but the form still was "not updatable". I re-looked at the table and the
autonumber sequence in the table was randomized rather than the generally
sequential arrangement. Several Ids in the 1,000's range, followed by some in
the 10's, some in the 100's, then more in the 1,000's, etc.

Does anyone know how a table could become scrambled?

The Id values were still associated with the same records (based on a small
sampling) but the records were shuffled.
I ran reports using the back up and current be's, compared data and updated
the backup be (re-entered one days worth of data).

I'm back on the air but still concerned about why/how.

BTW using Access 2000

 

[Tony Toews [MVP]]

I opened the be database and began making backups of each table (copies).
The main (largest) table would not copy "Assigning a null value to a non
variant field".

How did you make the copy? Cut and paste? Import into a new MDB?

Looking at the table, I found one autonumber (Id) missing and the data in
the fields for that record corrupt.

Ok, that solves one problem.

I deleted it and the table copied fine,
but the form still was "not updatable". I re-looked at the table and the
autonumber sequence in the table was randomized rather than the generally
sequential arrangement. Several Ids in the 1,000's range, followed by some in
the 10's, some in the 100's, then more in the 1,000's, etc.

Does anyone know how a table could become scrambled?

The Id values were still associated with the same records (based on a small
sampling) but the records were shuffled.
I ran reports using the back up and current be's, compared data and updated
the backup be (re-entered one days worth of data).

What you see could've been misleading. It's possible the table, while
in datasheet view, was sorted by a different column. So if you
clicked on the auto number column heading it would then sort by the
autonumber field.

Tony

--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm