By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,396 Members | 2,501 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,396 IT Pros & Developers. It's quick & easy.

HELP: Access record ID's corrupted by WWW insert and updates, memo field may be culprit

P: n/a
I'm adding and updating records in an Access .mdb via WWW .asp page.
Authored in Dreamweaver 2004 MX.

Help is welcome on this one. I have a great set of pages that work
fine, but it seems that insert or update pages don't always work now
on some records . . .

It seems that when lots of text is shoved into a memo fields the
database ID for that record gets messed up. Intial record insertion
goes OK, but updating is then hosed.

Insert and update pages work OK, and "most" records will update. The
strange error I'm getting is:

--------------

Microsoft JET Database Engine error '80004005'

The search key was not found in any record.

------------

While pages still display the records on the WWW, the record ID is
glitched up in such a way that you can not longer edit the record . .
.. upon submission you get and errors like 'search ID not found in any
record.'

I'm told this may have to do with the field order in Access and upon
the submission page.

Has anyone run into this? Solution has something to do with moving the
memo fields to be listed last in Access and submitted last from the
WWW.

Have you ever heard of field order mattering upon insert and/or update
of WWW submissions to an Access database . . . where memo fields are
best to be at the end of the submission order . . . otherwise they may
glitch up the existing records upon updating?

I've had a couple sites where the ID key of records gets corrupted in
Access and I can no longer update certain records and need to run
compact/repair to get the dbase back to normal. But, the problem
re-occurs.
Nov 13 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.