J
Joop Muis \(WS\)
Hi,
We have an Access application consisting of a front end MDB containing the
application itself and a backend MDB containing the actual data.
The front end is started up from an other MDB (start_app.mdb) which checks
for updates of the front end (app.mdb) in an other map (./updates/app.mdb).
The problem is that it always worked fine, but now since a month or two we
have a kind of memory problem (I think). Sometimes the app.mdb crashes when
working in it (for instance when opening a detail form from a list of
addresses) After that this happened the problem re-occurs very frequently.
BUT... when we DO NOT start the app.mdb via start_app.mdb we do not have
this problem anymore. All users accessing the front end do this through
Terminal Service, so they all work on the same machine (this excludes
version differences).
Does anyone have a clou what can cause this?
Thanks in advance
Joop
We have an Access application consisting of a front end MDB containing the
application itself and a backend MDB containing the actual data.
The front end is started up from an other MDB (start_app.mdb) which checks
for updates of the front end (app.mdb) in an other map (./updates/app.mdb).
The problem is that it always worked fine, but now since a month or two we
have a kind of memory problem (I think). Sometimes the app.mdb crashes when
working in it (for instance when opening a detail form from a list of
addresses) After that this happened the problem re-occurs very frequently.
BUT... when we DO NOT start the app.mdb via start_app.mdb we do not have
this problem anymore. All users accessing the front end do this through
Terminal Service, so they all work on the same machine (this excludes
version differences).
Does anyone have a clou what can cause this?
Thanks in advance
Joop