On Fri, 18 Aug 2006 05:26:02 -0700, R-P wrote:

Thanks guys. I solved it by just using it as a text-input. I did still try
ss:mm:hh dd/m/yy (didn't work) and MM for months (didn't seem to be allowed).
Guess I'll try mmm or M.

mmm or mmmm will display the month; m or M will display the minutes

If that doesn't work and I am going to use/calculate with the data I'll use
Labview or so to extract the dates and times.

I'm still having problems understanding the input format vs. the cell
format. If I have entered a cell-format and the input is a textstring fitting
that format, then I really hope that the Windows Regional settings keeps its
claws off my data.....

You're hopes are in vain. As I wrote, the parsing of the input is determined
by the Windows Regional settings.


*: logical: I consider small to big or big to small to be logical (e.g.
ss-mm-hh-dd-MM-yy), anything else, like the American way of writing a month,
then day then year, is so incredibly unlogical....

The key to using a program is to know the rules by which it operates. These
may be different from the rules by which you hope it would operate.

As I also wrote, there seems to be a bug in the handling of mm in that, in your
example, it is displaying "minutes" where it should be displaying the month.
The rule seems to be that if a "m" or "mm" follows an "h", even though there
may be intervening characters, it will be interpreted as "minutes" and not as
"month".

This does not apply to mmm or mmmm since they are unambiguous.



--ron