Getting ajax error on grids with infinite scoll enabled

After upgrading to SC 9 and migrating an app from V8, When I scroll down in a grid with infinite scroll enabled , I get the following Ajax error: [TABLE=“class: scErrorTable, align: center, cellpadding: 0, cellspacing: 0, width: 1, height: 30”]
[TR]
[TD=“class: scErrorTitle, align: left”]Error[/TD]
[/TR]
[TR]
[TD=“class: scErrorMessage, align: center”]Undefined offset: 13[/TD]
[/TR]
[/TABLE]
On closer inspection (turned off ajax errors for the app) it gave me the actual line the error occurs in:

Error
Undefined offset: 13

Script: /var/www/html/myapp/_lib/lib/php/nm_data.class.php (750)

I do not know if this is because I have code in the OnRecord event, but nonetheless here is the lines that give the error,

(THIS IS SCRIPTCASE CODE, NOT MINE)
Here is Lines 750 to 758:
if ($dias != 0 && $dias == $dias_meses[$mes_1 + 1])
{
$dias = 0;
$meses++;
if ($meses == 12)
{
$meses = 0;
$anos++;
}

In my opinion this is a bug introduced in version 9 and should therefore be investigated by Netmake.

EDIT
This bug was also reproduced in a paginated Grid, the only thing they have in common is that they have advanced search enabled and custom code in the OnRecord Event.

Netmake ,I am not signing up for the BLACK HOLE you call support again, the fact that I have a valid subscription fo V9 should entitle me to some sort of support to get Bugs like this fixed, that is standard level 1 support for most SW companies. If someone has the email of someone that I can report this to, please feel free to share it here.

With Decimal for example lets say the field is defined with 11.2 (that is 11 characters with two characters after the decimal point). I will use the value “1.25” as an example here:

If this field was created and you did not change any settings for it then to get “1.25” you would have to enter “125” in the field otherwise you would get the PHP error “Undefined Offset”. I’ll admit it seams like a Scriptcase error, but it is not. It is strictly PHP. Remember a decimal field expects a value which means that the last two characters are after the decimal point.

Now if you go into the general settings for the field look for the “Autocomplete with zeros” property. If you check this then if you enter a single value for the field the decimal portion will be filled automatically.

Next look for the “Show a calculator” and “New Calculator”. Check these properties. Now when you enter a value it will appear exactly as entered through the calculator.

In Scriptcase as with PHP when you have defined a Decimal field it expects ALL characters. The decimal point is assumed.

I hope this helps.

Thanks, I will try your suggestion, The point is that this was a conversion from v8 to v9 , I did not change any of the code and would expect it to work as it did in v8 , and btw, it is not a form application these are GRIDS. But I will look at the decimal precision anyway, thanks for the clue.