Method 'Value' of object '_combobox' failed

  • Thread starter Thread starter Paul
  • Start date Start date
P

Paul

We have a multiuser Access 2003 application where the front end resides on
each users' C drive, and the back end is on a network server.

When some, but not all, of our users try to open a particular form, they get
the following error message, followed by a complete shutdown of the Access
application with the Send/Don't Send message to Microsoft:

Error: -2147417848 (80010108)
Method 'Value' of object '_combobox' failed.

If you click "Debug," it takes you to the first line of code in the form's
Load event, regardless of what it is. Even if it's a simple MsgBox command,
it will crash.

Again, this form only crashes on some users' computers,
but not on others.

I have also had different users log on different computers, and whether it
crashes or not is strictly determined by the computer, not the user.
And it doesn't seem to be a function of the computer's memory -
I checked for that.

I found several discussions on the Web about this error number, and they
talk about modifying the System Registry. That doesn't make sense because
this application is successfully running a number of forms on these same
users' computers, so I can't believe there's something special about this
particular form that require tweaking the System Registry on some computers,
but not others.

I'd appreciate any suggestions about how to solve this so all my users can
use this form.

Thanks in advance,

Paul
 
Here's a few things to try, Paul.
Most likely issues are listed first.

1. Service pack & hotfix
Check the SP of the machines where this fails:
Help | About ...
Is it different from the machines where it does not?
Make sure they have at least SP2.
If they have SP3, make sure they have this hotfix as well:
http://support.microsoft.com/kb/945674

2. Run this recovery sequence on the database:
http://allenbrowne.com/recover.html
It handles lots of issues, such as Name AutoCorrect, spurious objects, bad
VBA binary, and reference problems.

3. Get Access to rebuild this form
If the problem occurs with a particular form use the undocumented
SaveAsText/LoadFromText to get Access to recreate it for you. Steps:
http://allenbrowne.com/ser-47.html#SaveAsText

4. Change form properties
Where a form cannot display a new record (e.g. its AllowAdditions is No, or
it is bound to a non-updatable query), and it is filtered in such as way
that there are no records to display, its Detail section goes completely
blank. Controls in the Form Header or Footer still display, but Access gets
confused if you programmatically refer to their Value. Details:
http://allenbrowne.com/bug-06.html
In your case, since the crash is happening in Form_Load, it may be difficult
to see if this is the cause visually.
 
Alan,

I did notice that the computers that are having the problem running the form
have SP3 installed, whereas the others have SP2, so that's a good indication
it needs the service pack and hotfix as you explain in 1 below. I did
download it, but evidently I have to wait until tomorrow when our
administrators return, because I don't have admin rights on that machine.

I decided to run steps 2 and 3 because I've done a lot of development work
on this mdb file, and I've suspected it has some things that could use
cleaning up.

The form is still crashing on the SP3 machines, so I'm looking forward to
seeing if the hotfix will overcome the problem. I'll of course post a
message in any event.

Thanks for your help and suggestions.

Paul
 
Allen, you were right about the SP3. We ran the hotfix you suggested at

http://support.microsoft.com/kb/945674

and the form no longer crashes on the machines running SP3.

Thanks for providing the solution to this problem.

One last question: do you have any idea why one particular form would
require a fix, while all the other forms in the application run without a
problem? This form doesn't have any features, subforms, or VBA procedures
that don't also exist in the other forms.

Paul
 
It's hard to pin down exactly what causes the problem. It could be as simple
as the fact that the combo's RowSource has more columns than others.
 
jesus said:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!



IF YOU HAVE OPENED THIS REPLY YOUR PC WILL BE INFECTED WITH A TROJAN WORM
CLICK HERE TO DELETE VIRUS. IF LINK DOESN'T WORK THEN YOU ARE SCREWED



!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
 
Friends and friends around the world.
We are presenting the new messenger.
He will be in the commissioning by the friends that we indicate to use the
system.
Access the system by clicking the link below and register free.

You get something for using orkut?
You get something for using skype?
You gain something by using twiter?
You get algumaocisa for using facebook?

Enjoy this is your time!!

Sign up and join for free.


http://www.sqipcom.com/?ref=webempreendedor

http://stakeholder.sqipcom.com/user/webempreendedor
 
Back
Top