> open the pathname&"whatever_directory\AcroRd32.exe "& the pathname
> "whatever_directory\your.pdf"
I should probably clarify.
All I did with Director is check to see if Reader is installed and if not
then run the installer. After that the connection between Reader and
Director is finished.
Quit the Director movie and try to open a PDF file by double clicking it and
Reader gets corrupted. Open the application by itself then do whatever you
want and everything works fine. It does the same thing on Win 95, 98, NT,
and Me.
I'm guessing it's an installer problem. I got the installer off the Adobe
Acrobat CD we own, and it does the same thing if I install from Director,
or just run the installer solo. I'm going to try it with the downloaded
installers, but my problem is that the downloaded Mac installer is a Vise
Installer, and I'm not sure if I need to worry about seperate liscensing
issues with them.
I just wanted to know if anyone has any experience with Acrobat installer
issues like this. Btw, our client does have an Adobe liscense to distribute
Reader.
thanks,
kyle
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/lingo-l.cgi To post messages to the list,
email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED])
Lingo-L is for learning and helping with programming Lingo. Thanks!]
