I've created a couple of form queries modeled directly after the examples in the book and I'm having troubles with text IDs.

I have three tables that query with numeric IDs just fine, but when I try to use a text ID, I get the following alert:

I click OK and see a yellow arrow pointing to:
"Private Sbu cboSelectOwner_AfterUpdate()"
and Chr$(34) is highlighted in grey.

When I use the toggle breakpoint button it highlights the line that Chr$(34) is on in dark red. Is there something wrong with the syntax here? I have it written as:
Thank you,

xxxiii

A bit more study, trial and error this morning, and I keep having problems when using text IDs.

I replaced the Chr$(34) with """, which got it to run through the line; but when I select one of the combobox items, nothing happens.

However, I can scroll through the various combobox items using the navagation.

BTW, I'm using a lookup table for the combobox and a datasheet subform for the results. This setup works great when the search string is numeric.

VBA kept hanging on Chr(34) and Chr$(34), so I ended up using a double-double quote to return a single-double quote. Same result, different method.

Though my "workaround" was a success, I still don't know how to fix the Chr(34) issue. I read that it's a missing reference, but saw nothing on how to fix it.

I hope this helps someone someday.

Isn't character 34 (")? What happens when you use character 39 (')?
So that the WHERE evaluates to (owner = 'cboselectowner') once VBA runs through it?
ie: strSearch = "[owner] = '" & me.cboselectowner & "'"
or strSearch = "[owner] = " & chr(39) & me.cboSelectOwner & chr(39)

(Note: cboselectowner default value is text)

HTH,
Loralee

Actually, right now I'm more concerned with figuring out how to get the ascii character codes to work in access 2k. They seem to work fine in my other office 2k applications.