Property OleObjectBlob could not be set

[ousoonerjoe]

Line 2: Property OleObjectBlob in rptDiaries could not be set.
Line 2: Cannot load control rptDiaries.


It's an old issue that I have found very little resolution to out there. rptDiaries is a Crystal 9 report in a VB6 application. I have created a new compile box and pulled the source code down to do a test compile. When I went to run it, the above messages are reported in the rptDiaries.log file.

Any advice or suggestions are highly appreciated.

Thank you,

"If I were to wake up with my head sewn to the carpet, I wouldn't be more surprised than I am right now.

 

[BobRodes]

I have found strange things with Crystal. I don't know if this helps your situation, but I found that reports created on a Win2000 box could not be deployed to an XP box without errors. I had to recreate the reports on the XP box (simply by opening up the old ones--I could do this just fine--in the Crystal IDE and cutting and pasting the controls into a new report) to get them to work.

 

[ousoonerjoe]

Thank you for your reply, BobRodes.

Crystal is famous for it's squirrelly errors. I've run into that before, too. In this case, both boxes are XP (verified that both have the same release and versions). I really do not want to have to "rebuild" all the forms to make this thing work. Any other ideas?

"If I were to wake up with my head sewn to the carpet, I wouldn't be more surprised than I am right now.

 

[BobRodes]

I really didn't either, but I had to. Were the reports created on the same XP boxes, or transferred over from somewhere else?

 

[ousoonerjoe]

We pushed the source code up into Source Safe, then pulled it back down onto the new box through VB and it's internal Source Safe tools. I've done this many times before, but Crystal randomly decides it doesn't want to port over to a new machine. It seems to vary from app to app.

"If I were to wake up with my head sewn to the carpet, I wouldn't be more surprised than I am right now.

 

[BobRodes]

I suspect it's a matter of what opsys the actual report file was developed on.