integers being truncated

[Nisbet]

I am having a problem with some custom integer fields I have added to the accounts module. when I look at the detail view of an account the trailing zeros of a number are missing for example 7000 shows up as 7, 125000 shows up as 125. When I open the account with the edit view the zeros are present. Anyone have any ideas what is going on here?

The custom fields are set up as integers with a max size of 11 no default,min or max values.

I am running the open source version of Version 5.0.0b (Build 3150) on Apace with MySQL.


Thanks.

[Nisbet]

I did some more testing and have determined that it anything longer than three digits is being truncated in the detail view(543,654 is truncated to 543 for example). Anyone have any ideas as to what is going on here?

[kuske]

Is it ossible that you have a wrong setting in decimal symbol and 1000s separator?
Are they different? It looks as if the comma is used as decimal separator, so all behind the comma is truncated.

[Nisbet]

Thank you for responding to my question.

I have verified that the , is in fact the thousands separator and the . is the decimal separator. I checked this in both the local settings and my user account. The numbers show up correctly in the edit view and when I look at them in the database, so I am pretty much stumped.

[Nisbet]

I have done some additional testing with integer fields in a custom module I built. These Seem to function properly(as in not truncating the values in the detail view), At this point I am throughly confused.

[Nisbet]

So, no one has any ideas on what may be causing this issue???

[Nisbet]

I really need to get this issue figured out. Does any have any ideas at all?

[kuske]

Really no idea. Can you please post your diagnistic zip file here?
Perhaps this can help to analyze the problem.

[Nisbet]

here is the diagnostic file you requested.

Thank you for your assistance

[kuske]

The first I can siee is that your diagnostic file does not contain any information about your database.
This is very strange.
It seems that there is a communication problem to the database.
Even the logfile shows that there are some Soap legitimation problems.
The the problem be caused by a defective database?