M
Maury Markowitz
I was experimenting with an auditing trigger on one of our important tables.
After every change it inserts a record into a history table. When this was
turned on, Access started generating the "multi-step operation" errors.
Does anyone know what triggers this error? Is it simply the return of lines
like (1 row(s) affected)? Or is it that the insert trigger is changing
@@rowcount or some other thing that Access is tracking?
If anyone out there has used a trigger like this with an Access front end,
I'd like to hear from you.
After every change it inserts a record into a history table. When this was
turned on, Access started generating the "multi-step operation" errors.
Does anyone know what triggers this error? Is it simply the return of lines
like (1 row(s) affected)? Or is it that the insert trigger is changing
@@rowcount or some other thing that Access is tracking?
If anyone out there has used a trigger like this with an Access front end,
I'd like to hear from you.