New Forum | Previous | Next | (P-PDF) Developers
Topic: Object variable not set -- Automation Problems
Conf: (P-PDF) Developers, Msg: 55011
Date: 5/29/2002 05:09 PM
Has anyone else run into this problem before? I have just finished a VB program that uses IAC to open Acrobat in an external window using Automation calls, etc. designed to be installed on client machines with either the full version of Acrobat 5 or else Acrobat Approval installed. It worked fine on our development machines -- that is, machines with Visual Studio installed on them.
However, when I tested it on one of our more "bare bones" Win98 test machines with full Acrobat installed, it fails miserably, giving "Object variable or With block variable not set" errors on every single line where an Acrobat automation object is involved.
(Actually, the weird part is, it worked the first couple of times we used it after the first time we installed it, but then gradually started giving these errors, then stopped working. Now it won't work at all, no matter how many times we reinstall either the program itself or the entire system.)
We actually completely erase and reinstall the entire OS on this test machine each time (using "Ghost") before installing anything, (as is our custom with all our software that we test) so we really are starting with a clean slate.
I've tried reconfiguring my install script to include everything from simple VB runtimes to the full DCOM and MDAC packages, to no avail. I've tried it with and without the MFC dlls. I've tried it with and without the ATL dlls. Are there any other dependencies I might not even be aware of that anyone knows of? I have also tried checking and double-checking all of the OLE-type CLSIDs in the registry to make sure the entries point to the right app paths (and they do). All my OLE-type dll build numbers seem to match up ok. What else is there to check? I'm running out of ideas! The only thing I haven't tried yet, which I'm getting ready to try now, is to switch to late binding on all my Acrobat objects to avoid forcing the custom interfaces to be marshalled across process boundaries (I've heard this can sometimes "trick" a stubborn automation server into working) -- but I hate to have to do that because it's a sloppy programming practice and eats up memory.
It then occurred to me that maybe the problem is that the machine we are testing on, which is intentionally very "bare bones," is too "bare bones" (Celeron 333 Mhz, original Win98, 24MB RAM). Does anyone know if there is a minimum hardware or software requirement for Automation in Acrobat 5 to work, and if that could be part of the problem? If so, is this minimum requirement published somewhere so I can show it to our product management team?
Seriously, if anyone has had this problem before and knows something I'm overlooking, please do chime in!! Thanks!!