By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
425,790 Members | 1,398 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 425,790 IT Pros & Developers. It's quick & easy.

Application defined or Object defined error

P: n/a
I have an Access 2000 database running on a network in a Citrix
environment. The problem I am experiencing is that some users (not
all) get the above error message occasionally, sometimes just once or
twice a day, sometimes many times.

It seems to revolve around two forms that are kept open most of the
day. Form A has a list of tasks to be done by that user. This form
requeries it's recordsource on the timer event once every ten minutes
to pick up any new entries made by other users. Form B is utilised
when an item is actioned and on update will delete the record and
requery Form A to remove the actioned item. The error usually occurs
in Form B and results in all the bound controls losing it's data and
showing #NAME#. Any mouse movement over any of the bound controls
repeats the error message (this message is displayed from the On Error
event on the form - before introducing this trap, the error message
was "Invalid Object").

The only thing that can be done is to close Form B and re-load and,
usually, everthing is ok again (for a while). Sometimes all the forms
currently open seem to experience the same problem and the entire
database has to be closed on the workstation, then re-loaded.

Any ideas?

Ian
Nov 12 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
TC
It would be best IMO to *disable* the generic error handling, so you can
find the line where the error occurs. Then post the relevant lines of code,
and the error number & message.

HTH,
TC
"Ian Bailey" <im******@dsl.pipex.com> wrote in message
news:60**************************@posting.google.c om...
I have an Access 2000 database running on a network in a Citrix
environment. The problem I am experiencing is that some users (not
all) get the above error message occasionally, sometimes just once or
twice a day, sometimes many times.

It seems to revolve around two forms that are kept open most of the
day. Form A has a list of tasks to be done by that user. This form
requeries it's recordsource on the timer event once every ten minutes
to pick up any new entries made by other users. Form B is utilised
when an item is actioned and on update will delete the record and
requery Form A to remove the actioned item. The error usually occurs
in Form B and results in all the bound controls losing it's data and
showing #NAME#. Any mouse movement over any of the bound controls
repeats the error message (this message is displayed from the On Error
event on the form - before introducing this trap, the error message
was "Invalid Object").

The only thing that can be done is to close Form B and re-load and,
usually, everthing is ok again (for a while). Sometimes all the forms
currently open seem to experience the same problem and the entire
database has to be closed on the workstation, then re-loaded.

Any ideas?

Ian

Nov 12 '05 #2

P: n/a
Sorry, forgot to add one vital bit of info. I'm sure the problem is
caused by the requerying. In fact, I have disabled the On Timer event
on Form A and the problem disappeared (although one person did
experience the problem once during the day - a big improvement!).
Problem is, I can't explain why.

Ian
Nov 12 '05 #3

P: n/a
Ian
The code that runs on these two forms have full error handling. The
error message is not being generated by any code. The only way to trap
this message is via the generic error handling.

I'm sure the problem is caused by the requerying. In fact, I have
disabled the On Timer event on Form A and the problem disappeared
(although one person did experience the problem once during the day - a
big improvement!). Problem is, I can't explain why.

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
Nov 12 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.