Recently Converted to 2003 format

[Clois Beckwith]

I have both a Frontend and a backend database. The backend has all the tables
linked to the frontend. I am running a test of the database with one of my
employees who has the same permissions as the rest of the group. She is the
only one I am testing: Here is the problem, there are two buttons that when
she clicks on them, it brings up an "Save Action Cancelled" and when she
clicks on the OK button, it brings in the form like it is suppose to. I have
looked at the code and it appears to have no save feature written into the
code for the buttons. Macro security is set for LOW on both my machine and
her machine. The above problem does NOT occur on my machine when I go to the
same folder location on our network drives. Any ideas?

 

[Jerry Porter]

Clois,

It's also possible that code is running in the form when it starts to
open. In the design view of the form, look at the event procedures for
the form (especially Open, Load, OnCurrent).

If nothing's obvious, you might insert some testing code at various
places to track down when the error is occurring. The easiest (and most
obnoxious) way would be to insert MsgBox commands with different
messages at various places in the code. Then see which messages come up
before you get the error message.

Jerry

 

[Clois Beckwith]

I checked the form and buttons going to the form, and there is nothing as far
as Event Procedures in those positions......It sure does not make any sense.

 

[Jerry Porter]

The error could be happening:

1) Before the code behind the button is executed. This could happen for
example if a record is being edited in a subform when the button is
clicked.

2) During the button's code. If you haven't done so yet, try putting a
break point at the beginning of the code for one of the buttons, and
see if you can determine at what point in the code the error occurs.

3) In the 2nd form (that the button code calls up). The break point
from #2 above should help find that, too.

If the error is occurring somewhere in your code, you should be able to
find it by doing Ctrl/Break when the error message is displayed. This
should interrupt your code at the line with the error.

Jerry