malfunctioning OLE when compile in DLL

[jefferso...@gmail.com]

Hi guys,

I am attaching Adobe acrobat reader to a program I'm writing. To load
a file, I saw in this newgroup that you just use ole_1.object.loadfile
(filename) to load a PDF file to make it work. I am just wondering why
the code works if I compiled the program as PBD, but it gives me the
following error if I compiled it as DLL. How should the OLE be written
if I want to compile it as a DLL?

---------------------------
System Error
---------------------------
Error Number 35.

Error text = Error calling external object function loadfile.

Window/Menu/Object = <no group>.

Error Object/Control = <no class>.

Script = <no rout>.

Line in Script = 0.

thanks,
Jeff

[Scott Morris]

<jefferso...@gmail.com> wrote in message
news:72868443-0090-4072...@p2g2000prf.googlegroups.com...

> Hi guys,
>
> I am attaching Adobe acrobat reader to a program I'm writing. To load
> a file, I saw in this newgroup that you just use ole_1.object.loadfile
> (filename) to load a PDF file to make it work. I am just wondering why
> the code works if I compiled the program as PBD, but it gives me the
> following error if I compiled it as DLL. How should the OLE be written
> if I want to compile it as a DLL?

The quick answer is - don't compile to DLLs EVER, unless you have a very
good reason. And since you're asking this question in this manner, I must
assume that you haven't fully evaluated this option to understand the
trade-offs and issues (and there are many) that arise when you do attempt to
compile to DLLs. For most, it is an insignificant benefit/lots of problems
situation.

[harlynto...@quipuxsoftware.co]

What if the same problem occurs in a program that is NOT compiled in DLLs?