I have an ADP database that makes use of a stored procedure as a data set in it's code. The stored procedure has two date parameters that are in the format DD/MM/YYYY and are defined as datetime fields and have default values set.
This functionality has been working perfectly well in my Access 2000 ADP database (back end is SQL 2000) under Windows 95 and Windows 2000.
One of my users has had XP and Office XP installed and, whilst everything seems OK, when she tries to run the function that uses this procedure she gets the message:
"The conversion of a char data type to a datetime data type resulted in an out-of-range datetime value".
I've checked the regional settings and they are fine - DD/MM/YYYY and I've stepped through the code - the SQL Statement has the correct date format.
I'm really at a loss here, it sounds like it is the connection between either XP or Access XP and SQL 2000 that is causing a problem - has anyone come across this please?
Thanks in anticipation.
Painy
This functionality has been working perfectly well in my Access 2000 ADP database (back end is SQL 2000) under Windows 95 and Windows 2000.
One of my users has had XP and Office XP installed and, whilst everything seems OK, when she tries to run the function that uses this procedure she gets the message:
"The conversion of a char data type to a datetime data type resulted in an out-of-range datetime value".
I've checked the regional settings and they are fine - DD/MM/YYYY and I've stepped through the code - the SQL Statement has the correct date format.
I'm really at a loss here, it sounds like it is the connection between either XP or Access XP and SQL 2000 that is causing a problem - has anyone come across this please?
Thanks in anticipation.
Painy