cancel
Showing results for 
Search instead for 
Did you mean: 

Version incompatibility issue with Interop.SAPbobsCOM.dll in SBO 2004

Former Member
0 Kudos

Hi,

I have encountered an incompatibility issue in DI API 2004 across different patch level-versions. Originally, I developed an application in SBO 2004 pl4 environment. Now, some of the customers who were installing the application, notified me that the application has a login problem. It turned out that the CompanyClass.connect() method returns an error message "object reference not set to an instance of an object", when the DI API version installed in the production environment is higher (in this case, pl7) than the DI API version which was used in the development environment.

I figured out that the problem can be fixed by replacing the Interop.SAPbobsCOM.dll file in the application directory by a newer version that reflects the DI API that is installed in the system. However, it seems a rather lousy workaround, if the customer needs to manually replace the dll. Maybe the installer could be customized to "sniff" the correct DI API level, but this too would be a pretty kludgy solution.

Does anyone know a better solution to this problem ?

Regards,

Henry

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

normally this is not a problem as long as they don't change the signatures on the DI-API (which they said they wouldn't) but it appears in P5 they changed that signature... we noticed some enums that got added and a few minor changes.