Automation Error in replica

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

James Allen - 29 Jun 2004 23:05 GMT

I have an Access 97 database that is replicated to a
number of users. It is working normally for me, but when
my users open the data entry form it appears to open
normally, but they receive the following error which
effectively locks them up when they try to take any action:

"The expression On Exit you entered as the event property
setting produced the following error: Automation Error.
The expression may not result in the name of a macro, the
name of a user-defined function, or [event producer].
There may have been an error evaluating the function,
event or macro."

The strange thing is if
1) From the form you open the design view,
2) Then open the code view,
3) Recompile the codes (which there are no compile errors
generated),
4) Close the code view and
5) Finally switch back to the form view.Everything works
fine. That is until you close out of the db and reopen it
again. Then the problem may reoccur.

I don't have this problem occurring with the design master
or an intermediate replica on a common server. It only
occurs on a local copy for the user. They are running IBM
T20's & T23s with Windows 2000 professional.

If anyone has any ideas of what is going on, please send
me an email. jamesallen@isualum.com.

Thanks for the help.
Jim

Reply to this Message

Cheval - 06 Jul 2004 22:31 GMT

Without repeating Michka, Split the app into a backend
(tables) and front end (everthing else) as access
replication has a terrible time replicating anything but
tables.

>-----Original Message-----
>I have an Access 97 database that is replicated to a
[quoted text clipped - 32 lines]
>
>.

Reply to this Message

Steven Parsons [MSFT] - 20 Jul 2004 18:20 GMT

Hi Jim -

This is Steven from Microsoft Access Technical Support replying to your
newsgroup post.

It sounds to me like some database references are getting cleaned up when
the user goes to Design View and compiles the VBA project. However, if this
is a multi-user application, then this end-user may not have the exclusive
access necessary to save the compiled state, and Access may be silently
tossing out those changes as the user shuts down his session of the Access
application.

In a multi-user environment, it is a better solution to split the
application into frontend/backend, and replicate just the backend. However,
if you all users are accessing the same shared backend, this would beg the
question, "Why use replication?"

Replication is best for users who share data, but do not have access to a
share backend file. Instead, all users have there own personal copies of
the database, which they then bring back to a central location at some
point, and synch there own personal copies of the database with a central
"hub" database. If everyone has there own (non-shared) personal copies of
the database, then they should not be running into the problem as described
in the paragraphs above.

Please let me know if this solves your problem or if you would like further
assistance. I look forward to hearing from you.

Sincerely,
Steven Parsons [MSFT]
Microsoft Access Product Support Services
This posting is provided "AS IS" with no warranties, and confers no rights.
Get Secure! (http://www.microsoft.com/security)

Reply to this Message