Subject | Re: Date format problem Windows 7 |
---|---|
Author | Aage Johansen |
Post date | 2011-07-03T13:10:27Z |
Dave wrote:
<<
I recently moved to WIndows 7 from windows XP and am experiencing
some odd behaviour with regards the database I am using.
Specifically, the interpretation of the date on the 2 versions of
windows seems to be causing problems.
I am using Firebird 2:0 and IBExpert (latest versions.)
ON the XP machine on the same database - this query works (returns data.)
SELECT TRANSID,TRANSDATE,INTERNAL_REF,DELIVERYITEM,ARCHIVED from
INVOICE WHERE INVOICETYPE = 'INVOICE' AND (TRANSDATE BETWEEN
:ThisDate and :ThatDate) ORDER BY TRANSID DESCENDING;
ON the WIndows 7 machine (using the same database and same software)
the same statement does not return any rows.
I have checked the Display format and regional-specific settings in
the Windows control panel and it all seems correct a.
Any help would be much appreciated.
another newsgroup:
----------------------------------------------------
I have various Excel workbooks and Access databases originally created under
Microsoft Office 2007 (Windows Vista) and that I connect to using ADO (table
direct).
After moving my systems to a new computer running Windows 7 the date fields
are suddenly presented in format dd/mm/yyyy instead of the previous format
dd.mm.yyyy
I have verified that dd.mm.yyyy still is the "standard" setting also on my
new machine, and that this is the format used by Access 2010 and Excel 2010
(respective) when I look at the fields directly.
I have not (yet) recompiled the programs in which I use ADO (last compiled
under Delphi 2007), but I don't understand why this should make any
difference?
I shall appreciate any comments and/or suggestions.
----------------------------------------------------
The response was:
----------------------------------------------------
It is a known bug in Windows 7 installation program. When you specify
your regional settings during installation, they are not saved
correctly. To fix it, you need to change regional settings to some other
country, save them and then change them back. After this Delphi programs
will also get correct settings from Windows.
----------------------------------------------------
I've seen similar problems on Vista and Win7 (and even on an old
Win2k server (after a Windos update), while there were no problems on
my WinXP). These problems were solved by the procedure above: change
(and save) "regional settings" a couple of times.
hth
Aage J.
<<
I recently moved to WIndows 7 from windows XP and am experiencing
some odd behaviour with regards the database I am using.
Specifically, the interpretation of the date on the 2 versions of
windows seems to be causing problems.
I am using Firebird 2:0 and IBExpert (latest versions.)
ON the XP machine on the same database - this query works (returns data.)
SELECT TRANSID,TRANSDATE,INTERNAL_REF,DELIVERYITEM,ARCHIVED from
INVOICE WHERE INVOICETYPE = 'INVOICE' AND (TRANSDATE BETWEEN
:ThisDate and :ThatDate) ORDER BY TRANSID DESCENDING;
ON the WIndows 7 machine (using the same database and same software)
the same statement does not return any rows.
I have checked the Display format and regional-specific settings in
the Windows control panel and it all seems correct a.
Any help would be much appreciated.
>>Maybe Windows is pulling your leg... A similar problem appeared on
another newsgroup:
----------------------------------------------------
I have various Excel workbooks and Access databases originally created under
Microsoft Office 2007 (Windows Vista) and that I connect to using ADO (table
direct).
After moving my systems to a new computer running Windows 7 the date fields
are suddenly presented in format dd/mm/yyyy instead of the previous format
dd.mm.yyyy
I have verified that dd.mm.yyyy still is the "standard" setting also on my
new machine, and that this is the format used by Access 2010 and Excel 2010
(respective) when I look at the fields directly.
I have not (yet) recompiled the programs in which I use ADO (last compiled
under Delphi 2007), but I don't understand why this should make any
difference?
I shall appreciate any comments and/or suggestions.
----------------------------------------------------
The response was:
----------------------------------------------------
It is a known bug in Windows 7 installation program. When you specify
your regional settings during installation, they are not saved
correctly. To fix it, you need to change regional settings to some other
country, save them and then change them back. After this Delphi programs
will also get correct settings from Windows.
----------------------------------------------------
I've seen similar problems on Vista and Win7 (and even on an old
Win2k server (after a Windos update), while there were no problems on
my WinXP). These problems were solved by the procedure above: change
(and save) "regional settings" a couple of times.
hth
Aage J.