you can only run one instance of the combo box wizard at a time

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I continue to get that error message each time I try to add a combo field to
a form, although there is not another instance of the wizard running. I have
had this error in the past with other databases and it seemed to go away
eventually, but this time it appears to be here to stay. Any suggestions?
 
Just tried it but it didn't fix the problem. Thanks for trying. Any other
suggestions?
-Howard

Al Camp said:
Howard,
Have you tried the Tools/Repair the database.. or compacting?
hth
Al Camp
Click to expand...
 
Well, when in doubt... remove and reinstall Access.
But, that's really like saying "Take 2 IPLs and call me in the morning!"

Have you tried taking the "core" of the error phrase ("is already an
instance"?) and tried searching the web?

If you don't have any luck with that, or you don't get any more responses to
this post, try reposting... and include the exact error phrase.
hth
Al Camp

Howard said:
Just tried it but it didn't fix the problem. Thanks for trying. Any other
suggestions?
-Howard
Click to expand...
 
Hi Al,

None of this helped. I looked at the link and examined the references as she
suggested, but no luck. To search through all the code modules looking for
entry points, as she suggested, is beyond me. I'll just do what I did last
time. Create a new database and copy all the modules from this one. That
usually makes it go away in the short term. As there are several complaints
about this exact issue, perhaps it should be acted upon as a BUG in Microsoft
Access. Thanks anyway!

- Howard (Frustrated)

Al Camp said:
Howard,
Try...
http://www.accessmonster.com/uwe/Forum.aspx/access/29690/Access-2000-Wizard-fails
or
http://www.officefrustration.com/q-t_116831-wizard-errors.html

Al Camp
Click to expand...
 
OK Howard,
Sorry we couldn't help you out.
Al Camp

Howard said:
Hi Al,

None of this helped. I looked at the link and examined the references as
she
suggested, but no luck. To search through all the code modules looking for
entry points, as she suggested, is beyond me. I'll just do what I did last
time. Create a new database and copy all the modules from this one. That
usually makes it go away in the short term. As there are several
complaints
about this exact issue, perhaps it should be acted upon as a BUG in
Microsoft
Access. Thanks anyway!

- Howard (Frustrated)
Click to expand...
 
Back
Top