Automation Error problem

  • Thread starter Thread starter James Allen
  • Start date Start date
J

James Allen

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. (e-mail address removed).

Thanks for the help.
Jim
 
James Allen said:
I have an Access 97 database that is replicated to a
number of users.
Click to expand...

Replicating the backend containing the tables, relationships and
indexes is fine, although somewhat troublesome at times, but
replicating the front end objects is not what replication was designed
to do.

You should be distributing a separate FE linked to the backend for
your users.

Now do you even need to replicate the BE at all? Are all your users
on a LAN or are some on a WAN or dial up? If not a LAN then
replication can make sense.

You want to split the MDB into a front end containing the queries,
forms, reports, macros and modules with just the tables and
relationships. The FE is copied to each network users computer. The
FE MDB is linked to the tables in the back end MDB which resides on a
server. You make updates to the FE MDB and distribute them to the
users, likely as an MDE.

See the "Splitting your app into a front end and back end Tips" page
at http://www.granite.ab.ca/access/splitapp/ for more info. See the
Auto FE Updater downloads page
http://www.granite.ab.ca/access/autofe.htm to make this relatively
painless.. It also supports Terminal Server/Citrix quite nicely.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
-----Original Message-----


Tony Toews wrote:

Replicating the backend containing the tables, relationships and
indexes is fine, although somewhat troublesome at times, but
replicating the front end objects is not what replication was designed
to do.

You should be distributing a separate FE linked to the backend for
your users.
Click to expand...

Tony,
I considered a split but was unsure how to implement the
solution. I have several users that are remote and only
periodically connect to the LAN. They need the ability to
work locally and sync up once or twice a week.

Suggestions?
Jim
 
James Allen said:
I considered a split but was unsure how to implement the
solution. I have several users that are remote and only
periodically connect to the LAN. They need the ability to
work locally and sync up once or twice a week.
Click to expand...

You'd have to use a different method of ensuring they get a copy of
the FE if there are any changes.

But you'd still want to replicate the BE for them.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
Back
Top