Finance | Project Operations, Human Resources, ...

Bad VBA File Logging into GP

(0) Share

Report

Posted on by vloveira23

Hello All,

I am getting the following message when I log into GP 2016.

The Multi_Management.vba project references some objects that cannot be found. These objects are listed in the file: C:\Program Files (x86)\Microsoft Dynamics\GP2016\BSSI39.txt

Thanks in advance!

Victor

All responses (8)

Answers (0)

Richard Wheeler 75,730 on at

Like (1)

Report

RE: Bad VBA File Logging into GP

I am not aware of any way to remove a modified form. What I have always done is export the forms modifications per form. Then delete/remove the forms dictionary and them import only the ones you want to keep using. You need to find the Binary Stream forms. Look in your DYNAMICS.SET file for the name.
vloveira23 30 on at

Like (0)

Report

RE: Bad VBA File Logging into GP

It appears that it's a bad VBA file. I exported the file and there is nothing in it for SOP_Entry

The highlighted one has nothing in it,is it safe to remove it and if so, how?

Thanks,

Victor
vloveira23 30 on at

Like (0)

Report

RE: Bad VBA File Logging into GP
Richard Wheeler 75,730 on at

Like (0)

Report

RE: Bad VBA File Logging into GP

Look in that file and see what it lists and then compare that with what you find listed under Customization Status in GP. Tools->Customize->Customization Status). Did someone remove a forms dictionary. BSSI are Binary Stream tables tied to Multi-Entity Management. Look for a modify form for Binary Stream.
Suggested answer

Derek Albaugh on at

Like (0)

Report

RE: Bad VBA File Logging into GP

It's possible that the Binary Stream may have an alternate version of the SOP Entry window, which is why it is making a call to it, or the VBA on the window uses SOP Entry in a way.

Sometimes, if you have a package file of all the modified forms and reports and any forms and reports with VBA, you can have users log out of GP, move the forms and reports dictionary files into a backup folder along with the .vba files that are in the GP directory. Then, launch Dynamics GP and in the Customization Maintenance window, you shouldn't see anything listed at all. Import the package file back in and this will manually re-create the forms and reports dictionary files, along with any .vba files, then test the VBA project to see if you still get the same error.

Thanks
vloveira23 30 on at

Like (0)

Report

RE: Bad VBA File Logging into GP

It's calling for SOP_Entry:

'(L) CORS' of window 'Line_Scroll' of form 'SOP_Entry'

'(L) CustREQDate' of window 'Line_Scroll' of form 'SOP_Entry'

'(L) DisplayUOFM' of window 'Line_Scroll' of form 'SOP_Entry'

'(L) Extended Price' of window 'Line_Scroll' of form 'SOP_Entry'

'(L) LBS' of window 'Line_Scroll' of form 'SOP_Entry'

'(L) MKH' of window 'Line_Scroll' of form 'SOP_Entry'

'(L) PRICEPERLB' of window 'Line_Scroll' of form 'SOP_Entry'

'(L) SellingPrice' of window 'Line_Scroll' of form 'SOP_Entry'

'(L) SellingQTY' of window 'Line_Scroll' of form 'SOP_Entry'

'(L) SellingUM' of window 'Line_Scroll' of form 'SOP_Entry'

'(L) Unit Price' of window 'Line_Scroll' of form 'SOP_Entry'

'Component Sequence' of window 'Line_Scroll' of form 'SOP_Entry'

'Contract Line SEQ Number' of window 'Line_Scroll' of form 'SOP_Entry'

'Item Number' of window 'Line_Scroll' of form 'SOP_Entry'

'Line Item Sequence' of window 'Line_Scroll' of form 'SOP_Entry'

'Location Code' of window 'Line_Scroll' of form 'SOP_Entry'

'QTY' of window 'Line_Scroll' of form 'SOP_Entry'

'QTY Allocated' of window 'Line_Scroll' of form 'SOP_Entry'

'QTY Fulfilled' of window 'Line_Scroll' of form 'SOP_Entry'

'QTY Prev Invoiced' of window 'Line_Scroll' of form 'SOP_Entry'

'U Of M' of window 'Line_Scroll' of form 'SOP_Entry'

'(L) SellQTY' of window 'SOP_Entry' of form 'SOP_Entry'

'(L) StringM246' of window 'SOP_Entry' of form 'SOP_Entry'

'BSSI_Facility_ID' of window 'SOP_Entry' of form 'SOP_Entry'

'Customer Number' of window 'SOP_Entry' of form 'SOP_Entry'

'Location Code' of window 'SOP_Entry' of form 'SOP_Entry'

'SOP Number' of window 'SOP_Entry' of form 'SOP_Entry'

'SOP Type' of window 'SOP_Entry' of form 'SOP_Entry'

'Save Button' of window 'SOP_Entry' of form 'SOP_Entry'
vloveira23 30 on at

Like (0)

Report

RE: Bad VBA File Logging into GP

Thanks for the heads up!

Victor
Suggested answer

Justin Sutton on at

Like (0)

Report

RE: Bad VBA File Logging into GP

Hi Victor,

That is Binary Stream's product (Multi-Entity Management).

Although our community may be able to help, your best bet is to reach out to them here:

gpsupport@binarystream.com

You can get that same error within GP itself if fields were removed in VBA, or if a DLL or file was missing in the location expected. In this case the files it is looking for are related to MEM, so I cannot really point you in the right direction quickly like their support likely can.

That said, the community has many users of MEM and you can look into the file referenced in the error to see what objects it is looking for.

Thanks!