Form Designer

[JD Kromkowski]

There is still some kind of quirk. Here is Table field information (from status) Field list: =========== Name Type Format Indexed —- —- —— ——- TRInit string “3U” Date date “mm/dd/yyyy” indexed Amount number “9999.00” Description string “250W” Billed boolean “1” CMNo integer “999999.” indexed TimeId integer “9999999999” recid_ro_internal string “” indexed But attached is what the form looks like after I created the form. Why should the date display as 31/Oct/1994 (you can’t see the 94 because edit box was made too small. Why should the Amount, which is .30 display as .299999999999999999? But I close Personal (you know the bug already that prevents you from just closing and reopening form because the FD still has control of the db so you get the share error), and reopen then everything is OK.

[Michael]

On 29/01/2013 16:42, kromkowski wrote:
> There is still some kind of quirk.
>
> Here is Table field information (from status)
>
> Field list:
> ===========
> Name Type Format Indexed
> —- —- —— ——-
> TRInit string "3U"
> Date date "mm/dd/yyyy" indexed
> Amount number "9999.00"
> Description string "250W"
> Billed boolean "1"
> CMNo integer "999999." indexed
> TimeId integer "9999999999"
> recid_ro_internal string "" indexed
>
>
> But attached is what the form looks like after I created the form.
>
> Why should the date display as 31/Oct/1994 (you can't see the 94 because
> edit box was made too small. Why should the Amount, which is .30
> display as .299999999999999999?
>
> But I close Personal (you know the bug already that prevents you from
> just closing and reopening form because the FD still has control of the
> db so you get the share error), and reopen then everything is OK.
>

Hi John,

So the behavior occurs only when you first create the form, but sorts itself out once you reload it? I can have a look, it sounds
like something is being initialized and then applied to the form when it shouldn't be, although it may be fixed in the current rev
I have.

Ciao, Neil

[JD Kromkowski]

Here is another example. What possible could Simpol or wxwidgets be
doing to change .30 into a ludicrously long and nonsensical decimal.
While it does correct itself if you close down Personal and then reopen,
something is definitely messed up that one should ever get a result like
that.

[Michael]

On 01/02/2013 16:14, kromkowski wrote:
> Here is another example. What possible could Simpol or wxwidgets be
> doing to change .30 into a ludicrously long and nonsensical decimal.
> While it does correct itself if you close down Personal and then reopen,
> something is definitely messed up that one should ever get a result like
> that.
>

It is probably a value converted from Superbase. Superbase values are stored using floating point. As a result, they are not
really accurate values, instead they are approximations. The difference in both cases is probably nothing more than the display
format being used to show them.

SIMPOL natively has a different approach to fractional values.

Ciao, Neil

[JD Kromkowski]

On 02/04/13 1:14 PM, Neil Robinson wrote:
> On 01/02/2013 16:14, kromkowski wrote:
>> Here is another example. What possible could Simpol or wxwidgets be
>> doing to change .30 into a ludicrously long and nonsensical decimal.
>> While it does correct itself if you close down Personal and then reopen,
>> something is definitely messed up that one should ever get a result like
>> that.
>>
>
> It is probably a value converted from Superbase. Superbase values are stored using floating point. As a result, they are not
> really accurate values, instead they are approximations. The difference in both cases is probably nothing more than the display
> format being used to show them.
>
> SIMPOL natively has a different approach to fractional values.
>
> Ciao, Neil
>

It was from Superbase. I get it. I forgot that .3 can't be represented
as binary.

[Author]

Posts