I don't know either this one is Solomon standard's bug or customization's bug. What I'm curious is this bug will not happen in standard level but the customization is the simple one. I have an experience of this one while customized Cash Account Transaction and Purchase Order screen. I was only set the property for grid's property exactly enabled property. The enabled property on grid will be changed based on the header's condition. Actually the header's condition is also customization. For example:
I wrote this code in spread1_LineGotFocus_Event
if status = "H" then
if flagbudget = 1 then
call msetprop("cTranDate", prop_enabled, false)
...
call msetprop("...", prop_enabled, false)
end if
end if
The weird was on the next entry or after you cancel or open the others hold batnbr, the F3 or F7 functionality in trandate field will disable, but I could double right-click and unfortunately, the value will not be loaded in grid view, but it was loaded in form view. I could saw it. What is it?
Another example was when I customized Purchase Order screen, the same way with Cash account transaction, my qty field, will always reset to zero every I input the new one. Then I released the set property for this field, and luckily I got the error in unit price field :(. My unit price will reset to zero every I input the new one.
I don't know what I have to do next, my temporary solution was, I release the set property for the weird fields, but I added the validation by wrote a 'retval = errnomess' code. Is there any hotfix of this one?
