[AccessD] Error 3011

Dear Group,

I have used Database Creations' ezSmartSearch dialog box successfully in the
past. Beats the tar out of having to code it myself.

Anyway, I now have an application that we're developing in Access 2000. The
app will run under Access XP and XP Runtime. I do development on both my
office A2K w/s and on the client's AXP w/s.

I'm having trouble with the ezSearch dialog box in AXP. When a Find button
is clicked on the main data entry form, the ezSearch dialog box is opened
and a Combo Box on the form (called BySearchType) is filled with the records
in the table behind the main form. During the setup of the ezSearch form
there's a line of code that says:

    Me!BySearchType.SetFocus

followed by a .DropDown. Running this in AXP caused an error to the effect
of "cannot find field '|' on form." That's a vertical-bar character in the
single quotes. After clicking OK on the error the ezSearch dialog box opens
and everything is as it should be EXCEPT the BySearchType combo box hasn't
dropped down.

If I close ezSearch immediately and try clicking the main form's Find button
again, I get this error in AXP only:

The Microsoft Jet database engine could not find the object
'~sp_cezs_SmartSearch~sq_cFindSearchID'. Make sure the object
exists...blah-blah-blah.

At first I thought I'd try different ways to express the .SetFocus
method...same error sequence.

Then I looked in the MSysObjects table and found and object Named

    ~sp_cezs_SmartSearchPro~sq_cFindSearchID

Note the "Pro" part. I thought that maybe the MSysObjects table had gotten
out of sync somehow...I wasn't really aware that Access used that table
while executing methods until now. Anyway, I couldn't figure out any other
way to change the name in the MSysObjects table than to delete the object
from the ezSearch form, save the form, and then re-create the object on the
form again. No go. I get the same series of two errors.

Again, this is just in AXP. Right now, on my A2K w/s at my home office,
ezSearch works just fine...and the MSysObjects table shows that goofy object
with "Pro" in the name.

Any guidance you can give me? This is holding up the finish of a project and
I'm stumped.

Thanks,

Steve Erbach
Scientific Marketing
Neenah, WI

If architects built buildings the way programmers built applications, the
first woodpecker to come along would cause the end of civilization.