>>ldEndDate is declared as LOCAL, meaning that the report won't see it. Do you have any expression inside the report that access ldEndDate?
Good Morning Sylvain;
Thank you for your reply.
ldEndDate is LOCAL, and not a part of the report. I think the problem is related to the date type field, how the text box is initilized with {}, and what VFP 6.0 expects in the SQL statement. I have tried hard coding the date, and get a date error. Pain oh pain. I know it is something simple, like using the correct conversion function, but I have tried using several functions, with no luck. SET STRICTDATE TO 0 is being used, and SET CENTURY TO. Without those settings in the LOAD of the form, I get date errors.
If I use character information in the select statement, it works fine, so I know it is something related to the date data type.
Tom
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only