This content has been marked as final. Show 2 replies
Most likely possibility I see (though I can't explain why it would have happened) would be that :
#1 - The date/time format settings are different between the database server and the FDM/WEB server. One server might think date should be formatted mm-dd-yyyy wheras another is expecting yyyy-dd-mm. If you have access to the database, you should be able to confirm this. The 64K question would be why would this be an issue randomly as this should affect a lot of things?
Another remote possibility would be that for the particlar period in question, the value stored in the DB doesn't match the value in that query. Perhaps whitespace or something else was appended to the date and the query failed with no results which generated the error. A quick peek into this database table would confirm this quickly. I doubt this is the issue though due to the specifitivity of the error message.
You are right. Changing the date format in SQL Query Date Format Mask within the application (in Configuration Settings), to YYYY-MM-DD solved this issue. Thanks.