Date Handling Bug in Personal

[JD Kromkowski]

Beyond the whole mess with indexing a date field. If you enter “12 15 pm” it changes it to “12:15 am” Note the space instead of a colon. I developed a bad habit with Superbase of entered times with the space. Which you can still do with here except for this quirk. JDK

[Michael]

JDK wrote:
> Beyond the whole mess with indexing a date field.
>
>
> If you enter
>
> "12 15 pm"
>
> it changes it to "12:15 am"
>
> Note the space instead of a colon. I developed a bad habit with
> Superbase of entered times with the space. Which you can still do
> with here except for this quirk.

A quick question, did it change am to pm, or was that a typing error? As
for the other, if you define the display format to use a space, it
should retain it. The code that handles this reads the content,
interprets it, and then redisplays it using the assigned display format.

Ciao, Neil

[JD Kromkowski]

It actually changes "pm" to "am"

So if you type "12:15 pm" it will change it to "12:15 am".

In fact if you type in "12:nn pm" for nn equal 00 to 59 it will change it
to "12:nn am"

[JD Kromkowski]

I think the bug is actually worse. Don't have time to document fully, but
if you change the display format to 24 hour (i.e. uncheck am/pm) (and you
can make it apply – there is a different bug here noted below) and then
enter a time in pm format using "pm" (e.g. "12:42 pm") the whole thing
shuts down.

When trying to modify table and changing display format, you won't always
get OK or DISPLAY buttons (they remain disabled) until you change the
field to indexed (and back to not indexed if you don't actually want the
field to be indexed but just want to change the display format.)

[Michael]

JDK wrote:
> I think the bug is actually worse. Don't have time to document fully,
> but if you change the display format to 24 hour (i.e. uncheck am/pm)
> (and you can make it apply – there is a different bug here noted
> below) and then enter a time in pm format using "pm" (e.g. "12:42
> pm") the whole thing shuts down.

I will have a look. This is all from the code in the date library, time
library amd db1util actually, all of which are supplied in source. The
functions are val2string(), fieldval2string(), string2fieldval(), etc.

> When trying to modify table and changing display format, you won't
> always get OK or DISPLAY buttons (they remain disabled) until you
> change the field to indexed (and back to not indexed if you don't
> actually want the field to be indexed but just want to change the
> display format.)

Hmmm. That sounds like the problem is that the oncellchange is not
firing until after you leave the cell where you made the data type
selection. I will have a look.

Ciao, Neil

[Michael]

Neil Robinson wrote:
> JDK wrote:
>> I think the bug is actually worse. Don't have time to document
>> fully, but if you change the display format to 24 hour (i.e.
>> uncheck am/pm) (and you can make it apply – there is a different
>> bug here noted below) and then enter a time in pm format using "pm"
>> (e.g. "12:42 pm") the whole thing shuts down.
>
> I will have a look. This is all from the code in the date library,
> time library amd db1util actually, all of which are supplied in
> source. The functions are val2string(), fieldval2string(),
> string2fieldval(), etc.

I had a look at this, and it turned out to be a problem in the
assigntimeval() function. I have fixed this and checked it with a number
of different time values, so it should be ok now. It will be part of the
imminent release.

>> When trying to modify table and changing display format, you won't
>> always get OK or DISPLAY buttons (they remain disabled) until you
>> change the field to indexed (and back to not indexed if you don't
>> actually want the field to be indexed but just want to change the
>> display format.)
>
> Hmmm. That sounds like the problem is that the oncellchange is not
> firing until after you leave the cell where you made the data type
> selection. I will have a look.

I looked at this, although you may select a new value in a combo in the
grid, or enter data in the edit control in a grid position, the
oncellchange event does not fire until the edit control is exited, or in
the case of the combo box, until focus is placed on another cell.

Ciao, Neil

[JD Kromkowski]

I think that there is still a problem.

If I type in

"8:00 am"

it changes it to "12:00 am"

Obviously, that's not what you intended.

JDK

[Michael]

JDK wrote:
> I think that there is still a problem.
>
>
> If I type in
>
> "8:00 am"
>
> it changes it to "12:00 am"
>
> Obviously, that's not what you intended.

Weird. I will have another look. Thanks.

Ciao, Neil

[JD Kromkowski]

So that I am clear.

If you type in "8:00" it changes it to "8:00 am".

It is only if one adds the "am" that one gets the weird result.

JDK

> JDK wrote:
>> I think that there is still a problem.
>> >>
>> If I type in
>>
>> "8:00 am"
>>
>> it changes it to "12:00 am"
>>
>> Obviously, that's not what you intended.

[Michael]

JDK wrote:
> So that I am clear.
>
> If you type in "8:00" it changes it to "8:00 am".
>
> It is only if one adds the "am" that one gets the weird result.

Found it. I will be updating the installers tomorrow (Friday).

Ciao, Neil

[Author]

Posts