• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 325
  • Last Modified:

Access 2007 dates transposed on input

Have an Access 2007 database deployed on a terminal server (Server 2008).  Back end is Sql Server 2008.  

For most users entering dates, whether typed or picked from the date picker is fine.  For a couple there are 2 issues.  1.  Transposition to US style on entry.  2.  Reversal of date entry i.e. 21/03/11 being trasnposed to 11/03/21

When this was first noticed I had a look at the user profiles, some were set on US location, US keyboard etc., and once changed it solved the problem for a couple of users.  

More interestingly some of the MS Access languages were set to UK, some to US, how does this happen if the server was installed as UK throughout, or so I have been informed by the clients IT support.

There are still 2 users, where no matter what is done the dates are trasnposed on entry, specifically when entered from the keyboard instead of the date picker.

Please note for most users everything is OK!

Thnaks
0
Paul-bbc
Asked:
Paul-bbc
1 Solution
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
I would suggest you remove those two user Profiles and recreate them, and be very careful to select the correct language settings when doing so. It's possible that you've got some corrupt user profiles.

< how does this happen if the server was installed as UK throughout, or so I have been informed by the clients IT support.>

I'm not sure, but I'd bet it has something to do with the virutalization features of the Terminal Services environment. It's possible to install the SERVER as a UK language, but setup a desktop as as US language base.



0
 
als315Commented:
You should use this recommendation from Meinolf Weber:
http://social.technet.microsoft.com/Forums/en-US/windowsserver2008r2general/thread/66cf9743-7d09-4aeb-af2f-14338d7936a8/
It will work only for new creted profiles.
0
 
Paul-bbcAuthor Commented:
User profiles were removed, then re-instaled, now all OK with no changes required to Access front end or SQL server db settings.

Please note that even though it was possible to amend location, keyboard, language etc. at Control panel and Access options level this did not cure the problem, only recreating the profiles from scratch solved the issue.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now