Hello,
i just downloaded version 4.6.3. In my subfile i have incorrect values in my textboxes. The first record in the subfile is ok. But in in the second record the decimal position is shifted, so the values are too big.
I upload two screens to your server, so you can see the difference. I also upload the problematic screen in json-format.
In the screen of version 4.6.2 the (correct) values (in the second subfile record) are:
19%, 1.500,00, 285,00 and 1.785,00.
The screen in version 4.6.3 shows the percent value multiplied by 1000 and the other values multiplied by 100.
Dieter
Version 4.6.3 and higher: Wrong field content
-
dieter
- Experienced User
- Posts: 122
- Joined: Tue May 22, 2012 6:45 am
- First Name: Dieter
- Last Name: Schröder
- Company Name: Ecclesia Holding GmbH
- State / Province: Outside Canada/USA
- Country: Germany
- Contact:
Version 4.6.3 and higher: Wrong field content
- Attachments
-
- json (1).txt
- The problematic screen of version 4.6.3 in json form.
- (31.61 KiB) Downloaded 96 times
-
- correct values in the second subfile record.
- version 4.6.2.PNG (61.76 KiB) Viewed 857 times
-
- wrong values in the second subfile record.
- version 4.6.3.PNG (62.58 KiB) Viewed 857 times
Last edited by dieter on Thu Aug 29, 2013 3:54 am, edited 2 times in total.
-
dieter
- Experienced User
- Posts: 122
- Joined: Tue May 22, 2012 6:45 am
- First Name: Dieter
- Last Name: Schröder
- Company Name: Ecclesia Holding GmbH
- State / Province: Outside Canada/USA
- Country: Germany
- Contact:
Re: Version 4.6.3: Wrong field contents
Hello,
i just installed the latest version 4.6.4. The problem that the textboxes in the subfile show too big values, still exists.
Dieter
i just installed the latest version 4.6.4. The problem that the textboxes in the subfile show too big values, still exists.
Dieter
-
Karthik
- New User
- Posts: 13
- Joined: Tue Jun 28, 2011 11:00 am
- First Name: Karthik
- Last Name: Ramachandran
- Company Name: Summit Consulting Inc.
- Contact:
Re: Version 4.6.3 and higher: Wrong field content
We tried running the PUIFNDSTR command to identify fields that have a percentage in them to see if we could have the same issue. We tried scanning for units, % etc.. but the command is not identifying these strings. Property seach did not return anything either.
-
dieter
- Experienced User
- Posts: 122
- Joined: Tue May 22, 2012 6:45 am
- First Name: Dieter
- Last Name: Schröder
- Company Name: Ecclesia Holding GmbH
- State / Province: Outside Canada/USA
- Country: Germany
- Contact:
Re: Version 4.6.3 and higher: Wrong field content
The problem is not limited to percentage fields. In my screenshot you can see that also the other numeric fields in the second subfile record have a problem: The shown value of 150.000,00 is too big. The correct value is 1.500,00. It is a "normal" numeric field with 2 decimal positions. The Checkbox "Use 1000 Separator" is activated.
When i call this screen in the version 4.6.2, all looks good. In version 4.6.3 and 4.6.4 the values are too big.
Note: Here in Germany the decimal separator is a comma and the 1000 separator is a point. Maybe in other languages this is contrary. Maybe this problem only occurs in the German locale.
When i call this screen in the version 4.6.2, all looks good. In version 4.6.3 and 4.6.4 the values are too big.
Note: Here in Germany the decimal separator is a comma and the 1000 separator is a point. Maybe in other languages this is contrary. Maybe this problem only occurs in the German locale.
-
David
- Profound Logic Staff Member
- Posts: 690
- Joined: Fri Jan 04, 2008 12:11 pm
- First Name: David
- Last Name: Russo
- Company Name: Profound Logic Software
- Contact:
Re: Version 4.6.3 and higher: Wrong field content
Sorry for the problems here.
Yes, the problem is not with percentage units.
It's a problem that has to with European-style (comma) decimal separator. We have a fix for this now in development, we could supply you with a patch that you can install on top of 4.6.4 to correct it.
Please contact technical support for this.
Yes, the problem is not with percentage units.
It's a problem that has to with European-style (comma) decimal separator. We have a fix for this now in development, we could supply you with a patch that you can install on top of 4.6.4 to correct it.
Please contact technical support for this.
Who is online
Users browsing this forum: Bing [Bot] and 1 guest