Object doesn't support this property or method oBusObj.EditState

Posted By gordongraham over 8 years ago

Hi Everyone,

I have a simple script triggered on the Post Read event on Sales Order Header to check the edit state of the order. The script then goes onto disable the order date and ship date fields if the edit state is 1 and the user is a member of a particular role.

This work great in sales order entry.

A problem occurs when drilling down to sales order through customer maintenance or inventory maintenance.

The first time the user drills down on a sales order it works fine; however, if the user attempts to drill down into another sales order and error 88 error is encountered.

Any idea why it works the first time but not the second?

Here is an excerpt from the script.

'Script to control access to certain fields on existing sales order fields.

retVal = 0
RestrictedEdit = "N"
estate=0

'retVal = oBusObj.GetValue("SalespersonNo$", slsperson)
'retVal = oScript.DebugPrint("salesperson= " & slsperson)

if oSession.CompanyCode = "TST" then 'for testing only

estate = oBusObj.EditState

retval = oSession.AsObject(oSession.UI).Messagebox("","Estate " & estate)

If cBool(oSession.AsObject(oSession.Security).IsMember("SO_RestrictEdit")) then RestrictedEdit="Y"
' to check to see if the user belongs to the Sales security role

If RestrictedEdit="Y" and estate = 1 then
'If RestrictedEdit="Y" then
'Msgbox ("Restricted Edit: " & RestrictedEdit)
'retVal = oScript.InvokeButton("fldr.pHeader")

0 TomTarget over 8 years ago

Have you narrowed it down to which specific line is throwing the error 88?

Is your overall script creating any business objects and then not releasing them when the script finishes?

What version of Sage 100 are you on? Seems like I had something like this on a script around 4.4 or 4.5 where the script would work properly for about 4 or 5 times and then would fail after that apparently due to some sort of memory leak in providex. Later versions fixed the problem.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 gordongraham over 8 years ago in reply to TomTarget

It occurs when checking the value of the edit state, estate = oBusObj.EditState
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 gordongraham over 8 years ago in reply to gordongraham

No business objects are created, version 2015. Works fine in SO entry.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 TomTarget over 8 years ago in reply to gordongraham

This really doesn't explain it but might give a clue to a workaround.

Description for oBusObj.EditState is:

EditState property values (0=no record in memory; 1=Existing record; 2=New record). Useful if you only want to run logic for a new record. Read only cannot be set. (NOTE: This is also the return value of the SetKey() method.

Seems to me that if you are drilling down from customer maintenance or inventory maintenance then your result could never be 2=new record? Therefore if you can figure out where it is being called from you could just bypass that check. Not sure how you would do that, however.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Nishanth over 6 years ago

Hi

Were you able to resolve this, I have a similar problem. The script is on Purchase order header and works fine from Purchase order entry. But when PO is accessed from Item maintenance it errors out on the second drill down.

Thanks,

Nishanth
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 daburke over 6 years ago in reply to Nishanth

I tested a simple post read script on both PO and SO drilled down from Vendor/Customer and script worked on multiple drill downs and browsing while in drill down. Tested on 2015 5.20
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Sage 100

Object doesn't support this property or method oBusObj.EditState

COMMUNITY

COMPANY

PARTNERS

SUPPORT & TRAINING