G
Guest
Users run a macro that contains approx. 13 queries that run consecutively
until complete. The only criteria used is from 2 fields that are on a form
that remains open while the macro is running.
We have a front-end application using Access 2000,2002, 2003 (depending on
workstation) and the back-end is still Access 2.0 (size of db is approx
68,000KB). We have been doing this same process for close to 7 years.
On 3/17/06 it suddenly started to fail, because a counter that copied into
another table/field hit the max integer length the field was set for. I
changed the responsible field type to long integer, and things are still not
working correctly. The results are sometimes sucessful, sometimes partially
successful, and I can't pinpoint what is happening. I did compact/repair the
database after the change.
The only difference I can see other than the counter/field issue is that we
have increaser our user base for this application from 5 users to 10. We have
another database application that mirrors the problematic one (it is used for
a single territory) that is running fine. It is much smaller in size, and
only has 2 users. I have tried running each query seperately to see where it
is failing, but it's dfferent each time. Can it possibly be a user overload
type problem - or is my backend database too large?
until complete. The only criteria used is from 2 fields that are on a form
that remains open while the macro is running.
We have a front-end application using Access 2000,2002, 2003 (depending on
workstation) and the back-end is still Access 2.0 (size of db is approx
68,000KB). We have been doing this same process for close to 7 years.
On 3/17/06 it suddenly started to fail, because a counter that copied into
another table/field hit the max integer length the field was set for. I
changed the responsible field type to long integer, and things are still not
working correctly. The results are sometimes sucessful, sometimes partially
successful, and I can't pinpoint what is happening. I did compact/repair the
database after the change.
The only difference I can see other than the counter/field issue is that we
have increaser our user base for this application from 5 users to 10. We have
another database application that mirrors the problematic one (it is used for
a single territory) that is running fine. It is much smaller in size, and
only has 2 users. I have tried running each query seperately to see where it
is failing, but it's dfferent each time. Can it possibly be a user overload
type problem - or is my backend database too large?