amkbailey
asked on
Access ODBC error on date field Invalid Precision Value
We did an upgrade from Sage Business Works 6.0 to 7.0 and are using Access 2002 to run reports against linked ODBC tables. The reports ran fine until the upgrade. When I went into the Access database, I noticed that 4 of the linked tables were not opening up data correctly. They were showing #Name? in every field and I got an ODBC-call failed error on opening. I deleted those 4 tables and relinked them and now they open up correctly.
I am still having a problem running a report that used a date criteria from an unbound form. I get the following error: ODBC-call failed [Pervasive][ODBC Client Interface] Invalid Precision Value (#0).
I have isolated the field in the query giving me problems. It is a date field. The weird part is that if I use a single date such as #3/9/07# , the query runs fine. But when I try to do a Between [Enter start:] And [Enter end:] It fails. This is while running the query directly and ignoring the unbound form for now.
I am still having a problem running a report that used a date criteria from an unbound form. I get the following error: ODBC-call failed [Pervasive][ODBC Client Interface] Invalid Precision Value (#0).
I have isolated the field in the query giving me problems. It is a date field. The weird part is that if I use a single date such as #3/9/07# , the query runs fine. But when I try to do a Between [Enter start:] And [Enter end:] It fails. This is while running the query directly and ignoring the unbound form for now.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Sorry left off the Between. I also added 'Short Date' to the 2nd date. Works now. Thanks!
Oops, good catch.. sorry.
ASKER
1/1/07
3/1/07