| :: Dates and Foxpro :: (5) | Post a New Message | Post a Reply |
 Dates and Foxpro | Post a Reply |
from: Oxford, England
However I get a "Operator/operand type mismatch" when running a report that contains a filter with dates when connected to a FoxPro database.
I am sure that this is because FoxPro insists on surounding dates with braces {} in SQL Select Statements
e.g SELECT * FROM dbname WHERE datefield > {01/01/2005}
But if I put {01/01/2005} in the wizard I get "Invalid search condition"
Works fine with other types of databases and also if I subsequently refine the dates in the report output.
Any ideas?
Thanks
| Re: Dates and Foxpro | Post a Reply |
from: Washington, DC
-------------------------
Ghost
| Re: Dates and Foxpro | Post a Reply |
from: Oxford, England
 Re: Dates and Foxpro | Post a Reply |
from: Washington, DC
objWiz.DatabaseType = 3 'FOXPRO
objWiz.Init(strConn) -------------------------
Ghost
 Re: Dates and Foxpro | Post a Reply |
from: Oxford, England
However now that it is working I have come across another FoxPro oddity.
I'm in the UK and we use the date format dd/mm/yy. But I have to use mm/dd/yy when adding a filter but when refining the report output I have to use dd/mm/yy. This is just with FoxPro I have tried an Access database and that consistantly requires dd/mm/yy
I have set objWiz.DefaultDateFormat = "DD/MM/YY" but that just seems to effect the output.
Sorry to be a pest.