Property OleObjectBlob could not be set

[bradth]

I am currently using VBA with great plains. I have VBA and VB 6.0 installed on my local machine. In VBA I have created program that prints barcodes and uses the MSCOMM addin feature to send code through the comm port. When I export this code as a package and try to install this on other client machines that have great plains I receive the error "Property OleObjectBlob in frmSerialNumbers could not be set". I've made sure that all of the .dlls that MSCOMM uses are installed on the machine, and have tried this on multiple machines. Any idea what else would be causing this error? Thanks.

Brad

 

[xlbo]

surely you are using VB rather than VBA.

You use VB to create programs. VBA works WITHIN programs

As such, please post in a VB forum

 

[bradth]

No, I am using VBA. I am using VBA to write a program within great plains.

Brad

 

[xlbo]

but to export the code means you are using VB. VBA cannot be exported without being compiled. At any rate, the issue you see will be a far more common occurence in VB / .NET as it is common practice. I would imagine you would get a better response in a forum that regularly deals with compiling and exporting code......

 

[bradth]

No. This is how it works. My code is written in VBA, within great plains. After I test the code and make sure that my code/customization works properly, the code is exported from great plains into a *.package file. This file is then imported onto other uses machine that are using great plains to update their code to use the current code/customization. When I import the code onto their machine, I receive the error.

Brad

 

[xlbo]

so how does that negate anything I have said about getting a better reponse in a forum where people are used to doing this???

a *.package file is not VBA though. VBA compiles into .dlls or .bas files

You have a license issue - this link (simple google search btw) seems to be relevant:

http://www.codecomments.com/archive337-2005-11-711328.html