Vexing automation problem

D

dgmoore

I have a process that employs Access2K to control Project03 under Win2K
Pro. After years of stable operation, the process has begun to throw
random errors that suggest problems with communication between Access
and Project. The errors are not consistent, and are popping up randomly
at different points in the process from one session to another. They
include (not necessarily all in the same session):

....Server threw an exception
....Invalid memory location access
....Remote procedure call failed
....Method FileSave of object...failed
....Method ViewApply of object...failed
....No field called [fieldname] found

These sometimes occur at the very beginning of a process, when Access
creates the Project object; sometimes when Project is opening the table
in Access to get data; sometimes after the data has been exported to
Project and saved; sometimes when starting to generate a series of
Gantts; sometimes when far into generating a series of Gantts; and
sometimes when Project is finished and is being closed.

The dialog "Microsoft Project encountered an error and needs to
close..." often appears at the end of processes that call Project.

I have rebooted the workstation and reinstalled Project and Office with
all service packs. I also created an environment on a different
workstation to see if the specific platform is the problem, but the
errors occur on the second w/s as well.

We have not been able to identify any O/S, DCOM, or Security Policy
settings that have occurree recently. This has us stumped - any insight
would be appreciated.

Thanks
Dave
 
R

Rod Gill

You've re-installed, so the next culprit may be cleaning up at the end of
each macro. Objects should get cleaned up automatically when a sub ends, but
this may not happen immediately or cleanly. Good practice is to force all
object variables to Nothing at the end of each sub.

Is there one particular part of your macro that causes problems? If so, can
you paste the code?

If you upgrade a PC to Access 2003 does that solve the problem?

If you go back to Project 2000 does that solve the problem?

How does Project 2003 communicate with Access, DAO or OLEDB?
Do you have the latest MDAC which I think is 2.8? If you do, can you rewind
to 2.7 or earlier and does that help?

When I have a problem like this where I can't find the solution I start
trying to prove what it isn't.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top