ODBC issue using a parameter or filter

[Brad Tornberg]

This is a bit strange but works fine with access tables
but NOT with ODBC. When I create a query using a hard
coded value for selection (i.e. = "486-66") my query
returns all data. If I try to use a parameter to be
inputted (i.e. [imputvalue] I get an ODBC error - call
failed. When I use the same approach with an access table
it returns whatever value I pass. On my ODBC it does not
seem to work. I even tried to use native SQL commands in
VBA and can't get it to work. Is it my ODBC setup? is it
an incompatibility with Pervasive SQL? if it works with
access tables why can't another table work when you can
get all recrds or select those with a hardcoded value but
not with an inputted value via a parameter entry? Help! I
can't go further until I get this resolved.

 

[david epsom dot com dot au]

I can't see your code, so I'm going to just GUESS
that you used "486-66" when you meant '486-66'

(david)

 

[Guest]

Yes of course.

-----Original Message-----
I can't see your code, so I'm going to just GUESS
that you used "486-66" when you meant '486-66'

(david)

This is a bit strange but works fine with access tables
but NOT with ODBC. When I create a query using a hard
coded value for selection (i.e. = "486-66") my query
returns all data. If I try to use a parameter to be
inputted (i.e. [imputvalue] I get an ODBC error - call
failed. When I use the same approach with an access table
it returns whatever value I pass. On my ODBC it does not
seem to work. I even tried to use native SQL commands in
VBA and can't get it to work. Is it my ODBC setup? is it
an incompatibility with Pervasive SQL? if it works with
access tables why can't another table work when you can
get all recrds or select those with a hardcoded value but
not with an inputted value via a parameter entry? Help! I
can't go further until I get this resolved.

.