Forums
This topic is locked
Some records won't update, weird error
Posted 14 Jun 2004 05:45:25
1
has voted
14 Jun 2004 05:45:25 Bob Brammer posted:
Hello,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.
/cms/calendar_update.asp, line 143
I'm using a map path and it works. The page contains AspUpload, Smart Image and Adv. HTML and the work GREAT.
Could this error be tied to Access? I download the .mdb and it seems fine. Many records WILL update. Very odd.
Replies
Replied 23 Jun 2004 18:29:16
23 Jun 2004 18:29:16 Marcellino Bommezijn replied:
Found some topics elsewhere. Maybe they help you out.
www.webwizguide.info/asp/faq/access_database_faq.asp#FAQ10
forums.aspfree.com/t18419/s.html
It looks like it has something to do with ODBC/ADO or/and the cursor location(?)
Hope this helps.
www.webwizguide.info/asp/faq/access_database_faq.asp#FAQ10
forums.aspfree.com/t18419/s.html
It looks like it has something to do with ODBC/ADO or/and the cursor location(?)
Hope this helps.
Replied 23 Jun 2004 19:10:03
23 Jun 2004 19:10:03 Bob Brammer replied:
THANKS, your post verifies a LOT of work!!!
We found both the dbf corrupted and ran repairs, but also found one field with an added space.
This links describes it.
forums.aspfree.com/t18419/s.html
It seems that the problem just compounds itself in a sort of loop as you try and debug it . . . you know something is off, but can't narrow it down, i.e., we repaired the data . . . re-ran submssion . . . re-repair . . .
I believe it was that one field name of mine that threw it sideways. GEEEZ!
Thanks for the great links that validate what we found.
We found both the dbf corrupted and ran repairs, but also found one field with an added space.
This links describes it.
forums.aspfree.com/t18419/s.html
It seems that the problem just compounds itself in a sort of loop as you try and debug it . . . you know something is off, but can't narrow it down, i.e., we repaired the data . . . re-ran submssion . . . re-repair . . .
I believe it was that one field name of mine that threw it sideways. GEEEZ!
Thanks for the great links that validate what we found.