" There was an error executing the command"

[tracktraining]

Hi All,

I created a db which has a switchboard with 4 forms and 4 reports options. I
turned it into a mde and thus allowing other people in my company to use it.

For a couple of my coworkers, one of the 4 forms on the switchboard is not
working (always the same form and same computer). The form is unable to open
and gives the following error message "There was an error executing the
command". when I tried opening the forms on other coworkers computer, it
worked (it opens).

Please provide some suggestions/advices/comments.

Thanks,
Tracktraining

 

[ruralguy via AccessMonster.com]

You need good error handling in all of your procedures when you convert to an
MDE otherwise you get that generic error message and Access closes.

 

[tracktraining]

How do i know that my error handling is good or not? is there a "good error
handling" method?

 

[ruralguy via AccessMonster.com]

Good really means *everywhere*. Are you displaying an error message or at
least logging every error? I suspect you have a procedure that is throwing an
error that does not have an error handler in it so the Run Time is just
dumping you out to the OS.

How do i know that my error handling is good or not? is there a "good error
handling" method?

You need good error handling in all of your procedures when you convert to an
MDE otherwise you get that generic error message and Access closes.

[quoted text clipped - 14 lines]

 

[tracktraining]

thanks for the advice about adding error handling everywhere. I did that to
my code. Then I created an .mde. I ran the .mde on a coworker's computer, I
get this error "2544 Training Database can't find the you referenced in the
Object Name argument". How do i get to the reference location to see what
reference is missing if the computer doesn't have access installed? That
computer only have the runtime 2007.

thanks!
--
Learning

Good really means *everywhere*. Are you displaying an error message or at
least logging every error? I suspect you have a procedure that is throwing an
error that does not have an error handler in it so the Run Time is just
dumping you out to the OS.

How do i know that my error handling is good or not? is there a "good error
handling" method?

You need good error handling in all of your procedures when you convert to an
MDE otherwise you get that generic error message and Access closes.

[quoted text clipped - 14 lines]

Thanks,
Tracktraining

 

[ruralguy via AccessMonster.com]

This link may be useful:
http://www.accessmvp.com/djsteele/AccessReferenceErrors.html

thanks for the advice about adding error handling everywhere. I did that to
my code. Then I created an .mde. I ran the .mde on a coworker's computer, I
get this error "2544 Training Database can't find the you referenced in the
Object Name argument". How do i get to the reference location to see what
reference is missing if the computer doesn't have access installed? That
computer only have the runtime 2007.

thanks!

Good really means *everywhere*. Are you displaying an error message or at
least logging every error? I suspect you have a procedure that is throwing an

[quoted text clipped - 9 lines]

 

[tracktraining]

thanks!
--
Learning

This link may be useful:
http://www.accessmvp.com/djsteele/AccessReferenceErrors.html

thanks for the advice about adding error handling everywhere. I did that to
my code. Then I created an .mde. I ran the .mde on a coworker's computer, I
get this error "2544 Training Database can't find the you referenced in the
Object Name argument". How do i get to the reference location to see what
reference is missing if the computer doesn't have access installed? That
computer only have the runtime 2007.

thanks!

Good really means *everywhere*. Are you displaying an error message or at
least logging every error? I suspect you have a procedure that is throwing an

[quoted text clipped - 9 lines]

Thanks,
Tracktraining

 

[ruralguy via AccessMonster.com]

Glad I could help.

thanks!

This link may be useful:
http://www.accessmvp.com/djsteele/AccessReferenceErrors.html

[quoted text clipped - 12 lines]