Found a large bug in the system and it has been fixed as of today
Took me a while to figure it out but my work with Stebbins discovered this as well as my attempts to enter data into Bodega’s RAMS system.
The value for UserDays was not correct.
To calculate this value we call this function
In the past this function was removing the decimal value as it was entered in as an INT
PARAMETERS ActyBeg date, ActyEnd date, PerBeg date, PerEnd date, ActualCount int, ActualDays int
I have changed these to
ActyBeg date, ActyEnd date, PerBeg date, PerEnd date, ActualCount float, ActualDays float
And instead of getting a smaller value (1080) I am now getting the correct value of (1090)
Now be aware that this issue will ONLY affect users that put in MANUAL user days instead of letting the computer calculate it from the dates of use (which will result in an integer value always). When you put in a MANUAL DAY USE in the User(s) Day Total it converts the ActualDay into a decimal value so that the calculated User Days will result in what the user wants it to read. User enters 1090 thus actualdays gets converted to 40.370 so that 27 * 40.370 will equal 1090.