J
JW
I'm maintaining a legacy application that interfaces with Microsoft Project
client using the Microsoft Project Object Library COM interface, whose
interface is exposed through MSPRJ.OLB. The application is a standalone
Visual Basic application.
In Project 2007, when the Project 2007 client application is closed and the
VB program tries to open a Microsoft Project file (.mpp file) using the
'Application.FileOpen' method, the method fails with the following error:
"Automation error: The server threw an exception. Some options may be
unavailable."
However, if the Project 2007 client was opened before this call was made by
the user, the FileOpen method works fine. In older versions of Project,
Microsoft Project client didn't need to be running for the FileOpen method to
work.
Is this a bug in the new Project 2007 version? Or does some other method now
need to be called before calling FileOpen?
client using the Microsoft Project Object Library COM interface, whose
interface is exposed through MSPRJ.OLB. The application is a standalone
Visual Basic application.
In Project 2007, when the Project 2007 client application is closed and the
VB program tries to open a Microsoft Project file (.mpp file) using the
'Application.FileOpen' method, the method fails with the following error:
"Automation error: The server threw an exception. Some options may be
unavailable."
However, if the Project 2007 client was opened before this call was made by
the user, the FileOpen method works fine. In older versions of Project,
Microsoft Project client didn't need to be running for the FileOpen method to
work.
Is this a bug in the new Project 2007 version? Or does some other method now
need to be called before calling FileOpen?