Format Property bug: "hh" doesn't display leading zero

It fails for me in 97 2000 2002 2003 and the beta.
Regional Settings h:nn
Format property hh:nn
Displays 9:11 not 09:11

I filed this as a bug in the beta, which they acknowledged and said it would
not be fixed in this version.


--
Joan Wild
Microsoft Access MVP

Brendan Reynolds wrote:
Thanks Rick. I can reproduce that in Access 2000, but not in Access
2003. So it looks like it may have been fixed in either Access 2002
or Access 2003. I don't have an installation of Access 2002 available
to test.
My tests also involved two different versions of Windows. Access 2000
is running on Window 98, Access 2003 on Windows XP SP2. So I can not
rule out the possibility that the problem may be related to the OS
version.
--
Brendan Reynolds
Access MVP


"Rick Brandt" wrote in message
om...
Brendan Reynolds wrote:
Seems to work as documented for me. Tested in both Access 2003 and
Access 2000. Here's the result ...

http://brenreyn.brinkster.net/format.jpg

You made me look Brendan. Apparently if your regional settings in
Control Panel are set up with hh: instead of h: then it works. Without
that then (Access 97 at least) definitely ignores the
leading zero on the hour even when the format property calls for it.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

You should be able to override the default by applying a format. For
instance, you can format hours as a single digit even if the default is
2-digit. I hesitate to label apparent anomalies as bugs, but this could
well be a bug. If you change the default that format will apply to any time
fields to which you have not applied formatting.
For the other question about the identifier, if you are using a newsreader
such as Outlook Express there is a setting in there. In OE6 you would go to
Tools Accounts. Click the News tab, click the account name to select it,
and click Properties. Click the General tab, and see what is in the Name
box. That will be the identifier used in the group, I believe. If it is
blank, I suppose it would default to the e-mail address, which you should
spoof in any case since it is part of the message.

wrote in message
ps.com...
Bruce, Rick, Brandon:

I changed my Regional Settings to "hh:" and voila, and it was
displaying "08/17/2006 01:45" when I switched back to the Access
window.

I had the problem running Access 2000 on Windows 2000.

Now I'm going to have to figure out the implications of changing the
default. I'm under the impression that the whole point of the Format
Property is to override the default.

Thanks for your solution to the mystery!

[Any idea why my identifier is my e-mail address?]

I just reproduced it, in Access 2003, on the very same system on which I
could not reproduce it earlier. I'm afraid I have no idea what I did
differently this time. Well, there is one thing I did differently. I
experimented with changing the case, I changed 'H' to 'h'. But even after
changing it back, I can still reproduce the bug now.

--
Brendan Reynolds
Access MVP

"Joan Wild" wrote in message
...
It fails for me in 97 2000 2002 2003 and the beta.
Regional Settings h:nn
Format property hh:nn
Displays 9:11 not 09:11

I filed this as a bug in the beta, which they acknowledged and said it
would not be fixed in this version.


--
Joan Wild
Microsoft Access MVP

Brendan Reynolds wrote:
Thanks Rick. I can reproduce that in Access 2000, but not in Access
2003. So it looks like it may have been fixed in either Access 2002
or Access 2003. I don't have an installation of Access 2002 available
to test.
My tests also involved two different versions of Windows. Access 2000
is running on Window 98, Access 2003 on Windows XP SP2. So I can not
rule out the possibility that the problem may be related to the OS
version.
--
Brendan Reynolds
Access MVP


"Rick Brandt" wrote in message
om...
Brendan Reynolds wrote:
Seems to work as documented for me. Tested in both Access 2003 and
Access 2000. Here's the result ...

http://brenreyn.brinkster.net/format.jpg

You made me look Brendan. Apparently if your regional settings in
Control Panel are set up with hh: instead of h: then it works. Without
that then (Access 97 at least) definitely ignores the
leading zero on the hour even when the format property calls for it.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

I implemented Rick Brandt's suggestion (thanks Rick) to put a properly
formatted [with the Format Function] TextBox on top of the editable
one, and it worked just fine, but the difference between the editable
display and the Input Mask (All DateTimes WILL have an input mask!)
caused no end of user confusion, so I blew it off.

For what it's worth:

Format Function for Visual Basic 6.0 Users
msdn2.microsoft.com/en-us/library/wb216dct.aspx

User-Defined Date/Time Formats

and

Format Function Changes in Visual Basic (Visual Basic .NET)
msdn.microsoft.com/library/en-us/vbcn7/html/vaconFormatChangesInVBNET.asp?frame=true


Visual Basic Language Concepts

Format Function Changes in Visual Basic

Date/Time Format

both have:

Visual Basic 6.0

"The characters "H[sic]h" display the hour as a number with leading
zeros,..."


The Microsoft Office Access Help Topic "Format Property - Date/Time
Data Type" makes no reference to an upper-case "H" format symbol, and
any attempt to use it in the Format Property string results in it being
changed to an lower-case "h", which, as has been demonstrated, behaves
unexpectedly when used in "hh".


This same Topic also makes the statement:

"Custom formats are displayed according to the settings specified in
the regional settings of Windows. Custom formats inconsistent with the
settings specified in the regional settings of Windows are
ignored[sic]."

This is somewhat bizarre in that the specific purpose of the Custom
Formats provided by the Format Property is to override the default
format specified in regional settings and make them "inconsistent with
the settings specified in the regional settings of Windows".

About the uppercase 'H' vs. lowercase 'h' - that's in the Control Panel
Regional Options time format, not in the Access Format property or the VBA
Format function. My apologies if I did not make that clear.

--
Brendan Reynolds
Access MVP

wrote in message
ps.com...
I implemented Rick Brandt's suggestion (thanks Rick) to put a properly
formatted [with the Format Function] TextBox on top of the editable
one, and it worked just fine, but the difference between the editable
display and the Input Mask (All DateTimes WILL have an input mask!)
caused no end of user confusion, so I blew it off.

For what it's worth:

Format Function for Visual Basic 6.0 Users
msdn2.microsoft.com/en-us/library/wb216dct.aspx

User-Defined Date/Time Formats

and

Format Function Changes in Visual Basic (Visual Basic .NET)
msdn.microsoft.com/library/en-us/vbcn7/html/vaconFormatChangesInVBNET.asp?frame=true


Visual Basic Language Concepts

Format Function Changes in Visual Basic

Date/Time Format

both have:

Visual Basic 6.0

"The characters "H[sic]h" display the hour as a number with leading
zeros,..."


The Microsoft Office Access Help Topic "Format Property - Date/Time
Data Type" makes no reference to an upper-case "H" format symbol, and
any attempt to use it in the Format Property string results in it being
changed to an lower-case "h", which, as has been demonstrated, behaves
unexpectedly when used in "hh".


This same Topic also makes the statement:

"Custom formats are displayed according to the settings specified in
the regional settings of Windows. Custom formats inconsistent with the
settings specified in the regional settings of Windows are
ignored[sic]."

This is somewhat bizarre in that the specific purpose of the Custom
Formats provided by the Format Property is to override the default
format specified in regional settings and make them "inconsistent with
the settings specified in the regional settings of Windows".

wrote:
I implemented Rick Brandt's suggestion (thanks Rick) to put a properly
formatted [with the Format Function] TextBox on top of the editable
one, and it worked just fine, but the difference between the editable
display and the Input Mask (All DateTimes WILL have an input mask!)
caused no end of user confusion, so I blew it off.

Ah well that's different. I consider InputMasks the work of the devil and
(almost) never use them.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com