Question Inconsistant Saving

[nuttychick]

I have an Access 97 backend and Access 2003 mde client.

One of the forms in this is database uses fields bound to a query to show the dates of a certain record and unbound fields to allow the user to suggest new dates.
The on click event of the save button uses SQL to save all this information to a table as a new record.
This is working fine on my own machine and a number of others, however there are a handful where the Dates from the bound qry fields refuse to be saved - all the other data is entered into the table but these fields are missing.

All users have the same version of the client and backend and we work within a controlled environment.

I am waiting to get the full version of MS Access on one of the effected workstations so that I can watch the code but until then I was wondering if anyone has seen this before?
Could it be related to different version of .dll or .ocx files??

Any suggestions much appreciated

 

[tmd_63]

As a thought. Have you checked the data format property of the machines themselves. Some suppliers set up Windows for you and use the US format instead of the UK format and vis-versa. This would cause a problem if you are trying to save a date record of 7th Day of the 25th Month instead of the 25th Day of the 7th month.

 

[gemma-the-husky]

see if the users that arent working have wrong regional settings

eg access may try to form the date into a valid US date that then breaks a table constraint

ie UK date 12/9/08, may get treated as UK date 9/12/08 because one of the terminals is set to US dates.

SQL triues to use US dates by default.

 

[nuttychick]

Thanks folks I will take a look, being in a controlled environment i would have hoped this was set by external measures but you never know!

 

[nuttychick]

Have checked the regional settings and we have no access to them in our environment, therefore they are all the same....

So I have got the full Version of MS Access 2003 installed on one of the workstations where the problem was occuring.

The problem is now fixed...

However this is not an ideal solution as it means allocating this software to about 60 users who dont really need it...anyone have any ideas??