Thanak you for your reply! Unfortunately the error occurs randomly and users
are all using different forms and performing different tasks in the
application. For the most part, it frequently happens when users have the
app minimized or leave it on the screen for a few minutes but it also
happens while they are actively using the system. It sometime occurs when a
user starts the application. Our network engineer says there is nothing
indicating a problem in the back-end re-synch logs. We are at a loss. Any
other thoughts would be invaluable. Thanks again Turtle!
- Mark
mweber_at_warrenlumber_dot_com
"MacDermott" <ma********@nospam.com> wrote in message
news:<pZ*******************@newsread2.news.atl.ear thlink.net>...
Is there any consistency as to when this error appears?
Is a particular form/report open?
Are your users performing a particular task?
Does it appear when your back-end resynchronization occurs?
- Turtle
"Mark A. Weber" <mw****@warrenlumber.com> wrote in message
news:10************@corp.supernews.com...
Hello everyone! This is my first post so please bear with me. We have
recently re-vamped an Access application such that in each of our 5
locations
a local SQL server receives published updates from our main office
server.
Remote servers also send their local updates to the master and they are
in
turn propogated to all of the other remote servers. The new design works
great except for one annoying bug we have been chasing for two weeks:
"Faulting application msaccess.exe, version 9.0.0.2719, faulting module
mso9.dll, version 9.0.0.2720, fault address 0x0007ee2d." When a user
gets
the
error, they hit close and it terminates Access. If they move the error
off
the screen and continue working the application continues. They have
discovered this and have been doing so but the fact that the error
appears
must be fixed. If anyone can point me in the right direction it would be
muchly appreciated. Thanks in advance!
- Mark
mweber_at_warrenlumber_dot_com
"MacDermott" <ma********@nospam.com> wrote in message
news:pZ*******************@newsread2.news.atl.eart hlink.net... Is there any consistency as to when this error appears?
Is a particular form/report open?
Are your users performing a particular task?
Does it appear when your back-end resynchronization occurs?
- Turtle
"Mark A. Weber" <mw****@warrenlumber.com> wrote in message
news:10************@corp.supernews.com... Hello everyone! This is my first post so please bear with me. We have
recently re-vamped an Access application such that in each of our 5
locations
a local SQL server receives published updates from our main office
server. Remote servers also send their local updates to the master and they are
in turn propogated to all of the other remote servers. The new design works
great except for one annoying bug we have been chasing for two weeks:
"Faulting application msaccess.exe, version 9.0.0.2719, faulting module
mso9.dll, version 9.0.0.2720, fault address 0x0007ee2d." When a user
gets the
error, they hit close and it terminates Access. If they move the error
off the screen and continue working the application continues. They have
discovered this and have been doing so but the fact that the error
appears must be fixed. If anyone can point me in the right direction it would be
muchly appreciated. Thanks in advance!
- Mark
mweber_at_warrenlumber_dot_com
