Sage 100

MAS v4.4...we have written a BOI script that works in MAS90 v4.4 on our test system without issue. We we try to run it on the clients MAS200 v4.4 environment we get the following error and the script fails: OLE Error Number: 424 Description: Object required: "" Language: VBscript Script Line: 88 Script Column: 4 oPrice = oSession.GetObject(""CI_Item.bus"") Any idea what could be going wrong or why it is different on MAS200 than MAS90?

Allow external access? Just had this

Yep, checked that. We have allow external access enabled in company maintenance.

Run on server vs client

Yep...tried that too. I am trying to find my notes from last years Summit session on BOI...I think I have tried everything from memory.

Post your script

Are you running this as a Button Link, Advanced Scripting (fires on an event), or just a CScript/WScript?

@AaronClark we are running from a button link on a screen. @ScottHickman I will post the script shortly. My vb person is troubleshooting it some more.

Just saw it: should it be CI_ITEM_BUS (or CI_ItemCode_BUS), not CI_ITEM.BUS? Although, why that would work on MAS90 and not 200 is beyond me.

Aaron, that might be just be my typo when typing the error back on the screen.

Ahhh... well. Darn. Thought I had the answer then. Did you get this figured out?

Not quite yet figured out. My vb girl is going through her code again. I will keep you posted.

my ""vb girl""????? Is this like your ""Bond Girl""....................

Jeff I do not know who she is - but she is KILLING me with the suspense... I have to see that code! LOL.

I have attached the script. As I said they work fine in a MAS90 environment but we get the error (also attached) in a MAS200 environment.

It looks like you are trying to update the standard cost. You cannot do that in 4.40 and above if the item has history.

I thought you could if the items are FIFO? Plus it worked in the MAS90 4.4 environment...We could see it successfully update the standard cost on our MAS90 4.4 w/ FIFO items.

Hahah...very funny @JeffSchwenk .

Is there some additional code where you are initializing the oSession object?

No there isn't Scott. Is their something we have to do differently with it for MAS200?

Seems like every time I had an issue with 200/90 is related to the path. ie., 90 was using a mapped network drive to the server whereas 200 was using a local drive on the server. I assume this is a script being launched from a custom office button or a MAS event?

Okay...we fixed the path to use a UNC on the button that launches (see attached), but now a new error. It looks to be a DSN issue even though we have the DSN setup on both the server and the workstation as a system DSN. Getting closer but still stumped.

Can you use the connection string instead of a DSN?

Are you trying to connect to a 64-bit DSN from a 32-bit application?

I will try to find the connection screen and use that instead. We are calling data from an Access database. I am pretty sure we are using the 32-bit DSN on both the server and the workstation.