Sorry, my typo.

strwhere = strwhere & "[queryobject.subject] LIKE ""*" & Me.Combobox & "*"""


--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)


"accessdesigner" wrote in message
...
Getting closer.... at least this time it did open the form, but it was
blank...

strwhere = strwhere & "[queryobject.subject] LIKE ""*" * Me.Combobox &
"*"""

i replaced *Me.Combobox with ... &Me.Combobox

but it did not read any data, it bypassed the statement completely and
just
opened the form.... but thats a start in the right direction, because at
first my statement locked the program and the form did not open at all...

"Douglas J. Steele" wrote:

That doesn't work because it's looking for the literal string
[Me.Combobox]
anywhere in your subject field.

Assuming you want the value that's currently selected in Combobox, you
need
to use:

strwhere = strwhere & "[queryobject.subject] LIKE '*" * Me.Combobox &
"*'"

Note the inclusion of single quotes in there. Exagerated for clarity,
it's

strwhere = strwhere & "[queryobject.subject] LIKE ' * " * Me.Combobox &
" *
' "

If it's possible that what's in Combobox is going to include apostrophes,
use the following instead:

strwhere = strwhere & "[queryobject.subject] LIKE ""*" * Me.Combobox &
"*"""

That's

strwhere = strwhere & "[queryobject.subject] LIKE " " * " * Me.Combobox &
"
* " " "

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)


"accessdesigner" wrote in
message
...
I will try that when I get back home.... I was trying to practice on my
work
version, which still doesnt work:

strwhere = strwhere & "[queryobject.subject]LIKE ''*[Me.Combobox]*"

it still wont work.....

"John Vinson" wrote:

On Sun, 26 Nov 2006 09:31:02 -0800, accessdesigner
wrote:

ty... ( need you all on speed dial.... lol)

my combobox is connected to :
SELECT Names.Name FROM [Names] ORDER BY [Name];
(thats a table where my list names scroll down from the combobox

The Query: NameThings .....is only connected to my Report

The word Name is a bad Name to Name a field or a control, since both
tables and controls have a Name property already!

Try changing the table definition so that you're using a nonreserved
term in place of Name - or at the very least bracket it.

The difference between the home and work versions *MIGHT* be because
one of them has Name Autocorrect set in the database's Options, and
the other doesn't. IN my experience this misfeature should be turned
OFF.

Perhaps you could post the complete SQL of the NameThings query, with
some indication of the datatypes of the table fields.

John W. Vinson[MVP]