I used your suggestion however the problem persist. The source table
(tblService) is set as a text field with the length set to 255. Here is the
rowsource for the cmbService:
SELECT tblservice.serviceID, tblservice.Service, tblservice.CategoryID,
tblservice.Description FROM tblService WHERE
(((tblService.CategoryID)=[]![CategoryID]));
In terms of my code, I have specified a variable (strfilter) as string.
Should I define strfiler in the code (eg: strfilter= "ServiceID=" &
me.serviceid)
Z
>I used your suggestion however the problem persist. The source table
>(tblService) is set as a text field with the length set to 255.
That doesn't parse. A *table* might contain a 255 byte text field, but saying
that "the source table is set as a text field" is meaningless. A table isn't a
field and can't be "set as" a field. I just don't understand what you mean
here!
> Here is the
>rowsource for the cmbService:
>
>SELECT tblservice.serviceID, tblservice.Service, tblservice.CategoryID,
>tblservice.Description FROM tblService WHERE
>(((tblService.CategoryID)=[]![CategoryID]));
I'm astonished that works at all. What is intended by the peculiar []!
syntax!?
>In terms of my code, I have specified a variable (strfilter) as string.
>Should I define strfiler in the code (eg: strfilter= "ServiceID=" &
>me.serviceid)
What does strFilter have to do with this combo box? Where is the value of
CategoryID supposed to come from? I'm simply not seeing the whole picture
here!
John W. Vinson [MVP]