>Alright! I know this question has probably been asked before but I'll ask it again...
>
>Here's my SQL Statement(either one gives the same results):
>
>Select * from customer where cCustName = ?vp_CustName
>
>Select * from customer where cCustName like ?vp_CustName
>
>If I execute this statement on a local vfp or fp table I get a dialog box just as expected. If I enter a value to populate the view parameter I get a set of records - just as expected. But, if I leave the view parameter empty shouldn't I get an empty record set? NO! I get the whole stinking table in my record set.
>
>However, If I perform either one of these queries throught ODBC and I leave the view parameter empty I get just as I expect - an empty record set.
>
>How can I get VFP 6.0 to treat a select statment as if it's running on ODBC? Or is this normal behavior and I should just shut-up, bite the bullet and code to this behavior?
SET EXACT ON
SET ANSI ON
in VFP will give you empty table.
If it's not broken, fix it until it is.
My Blog