Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Shaun E on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Attn Access Gurus: Odd Error with Random Memo Deletion

Status
Not open for further replies.

nkrst1

Programmer
Feb 13, 2001
49
US
Let's see how simple I can make this:

I have a form with a subform. The form has a memo field. The user will click from the SUBFORM to the memo field in the regular parent FORM. The user will then click from the memo field in the FORM to a field back in the SUBFORM. Once the user starts entering/changing information in the SUBFORM, the MEMO field in the FORM (not subform) gets deleted and the following error occurs:

"Update or Cancelupdate without AddNew or Edit"

Only options are OK or CANCEL, and it seems to fall in a continuous loop and the user cannot get out. The message keeps coming back.

I will have them go through the VB, but there was no option to debug (even a greyed out debug button).

Can't find a pattern to this behavior, either. What could possibly be happening? I'm not even sure where to look.

I've heard that MEMO deletion in Access is typical. Is this true? Are we suffering from an inherent problem with Access itself?

-Nish
 
Hello there
Could I ask
What version you are in
Are you using ADO or DAO

"Update or Cancelupdate without AddNew or Edit" indicates
you are using a recordset somewhere and this wasn't
indicated

Have you checked the order of things. Has the child side
of the form/subform link been edited before the parent

Or are you trying to create a new subform record which is
triggering another event

If a Recordset.Update is issued without first issuing an AddNew or an Edit method, vba correctly raises an error, because the Update method can only be invoked after an AddNew or an Edit method.

3020 is in the ACC95 reserved errors list
I'll try and help more when you reply

regards

jo

 
Thanks for the reply.

This db was originally written in access97 and was migrated to 2000 within the past year. Most of the code uses DAO.

It seems like the error occurs when in this order:

Child > Move to Parent field > Move back to child > edit field in child > Field in parent deletes and error occurs.

No new creation of a record, just an update.

I'm looking into the Recordset.Update issue. I didn't write this code, so I have to pick through a lot of stuff.

What do you mean by, "3020 is in the ACC95 reserved errors list"? Where would I find info on this?

-n-
 
I'm also wondering what's causing the deletion...

#Deleted

shows up in the memo field.
 
nkrst1,

Did you ever find out why you are getting #Deleted in the memo field? I am having the same problem. I think my 2 memo fields are just hosed. I get Write Conflict errors with them and #Deleted and #Error in the tbale when I try to edit them. Anyone else have experience with this? Am in a big bind. Thanks.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top