Bill,
I very much appreciate that you take the time and try to understand my
problem. So here is the story (Don't complain, you asked for it ;-)
My project (C# - I am a bit shy to mention this here as it always resulted
in a comment like "Forget C#, use VBA:-( As if I just picked C# because I
like the look of it) is an update of MSPS from timesheet data in SAP. I get a
flat file with a code wich allows me to identify the project and task and
resource (using a Stored Procedure on the MSPS DB). I have a value for hours
and cost. This will update Actual Work and Atual Cost.
I used the MS Project Object Model and COM Interop. Works fine! But this
only allowed me to open a project with <DataSourcename>/ProjectName. I can
not do a <>/Projectname since the MS Project Object Model doesn't allow me to
connect to a MSPS (even using MS Project Client, you can't connect to a MSPS.
You have to close MS Project and re-open it. I find that very strange!). Once
I opened the project, I retrieve a task object based on the information I got
directly from the DB. I then find the resource and update the values using
timescaled data. I then do a Project Close and publish the changes to the
server. This all workes fine. But then the problem started. During testing my
client found out that all projects where we did an automatic update show a
message box saying that there are local resources with the same name as
enterprise resources and whether they should be updated with the enterprise
resources. Further investigations showed, that with opening a project using
the procedure as described above, the resources are treated as local
resources.
So what was the solution? I tried to use the settings for openPool and see
if this does make a difference. But it didn't. And I was wondering what the
different parameter values actually do. Hence my question here in the group.
The solution so far? I re-worked the application and create a process in C#.
This process starts winproj.exe with the parameter /s <ProjectServerName>. I
then grab the object and create a MS Project Object from it. From there on it
is the same as before with one major difference: I can use OpenProject
<>/ProjectName since I am connected to a MSPS.
Quite honestly: I don't like the solution. It is clumsy and it actually
opens MS Project visuall yon the screen (even if I can minimize it, it is
still there). But it seems to do the job.
Because I am a person who is not satisified with the fact that something
just blows up but wants to know why it blew up, I am still wondering what the
parameters for openPool actually do.
Who would have thought that MS Project Automation is so much painful fun?
Cheers
Peter
William Raymond said:
Hi Peter,
Okay, I'm starting to understand where you are coming from. It sounds like
you need to describe in more detail what you are trying to accomplish. For
example, what do you mean by opening a project from the database? Are you
trying to open a project from a project database and save it to a Project
Server database (or Project Server database 'A' to Project Server database
'B' or same Project Server with direct DB access to sane Project Server
database using the front-end?)
This will help me understand what the issue is you are having. However, it
sounds like you are trying to import a project from one dataabse to a
Project Server database. You need to do a "Tools->Import Project to
Enterprise" and not a FileOpen/FileSave/FileClose.
Step me through the intent of the application and that should help me quite
a bit.
-Bill
--
William Raymond [MS Project MVP]
(e-mail address removed)
BLOG:
http://www.mympa.org/blog.aspx
PeterNZ said:
Hi Bill,
thank you for your reply and sorry that I haven't replied yet. But I was
buried ih the depths of my project.
The problem is (or better "was") that I open a Project from the Database
and
then publish it to the server. The next time a PM opens this project, he
gets
an message telling him that there are resources which are local and if he
wants to replace them with the Enterprise resources. I thought that I
could
fix this through the openPool parameter. But I didn't understand and
couldn't
find documenatation about the parameter values.
I meanwhile restructured my program and open MS Project in a process with
the parameter "\s ProjectServerURL" and open the project from the Server.
This honestly is a pain in the backside! It threw up all sorts of other
issues. But on the other side, it works! And the spec didn't say anything
about "The program has to be well designed and well implemented".
I am sorry to say that, but when I was told that I am now the expert for
MS
Project automation, I felt a strong urge to run as fast and as far away I
could.
Cheers
Peter
:
Hi Peter,
I would need more detail in how you are accomplishing this, but it sounds
like you might be adding resources durectly into the resource sheet by
name.
Even if they are Enterprise resources, Project assumes they are not until
you do a save (at which time it prompts you to conver the local resources
to
be enterprise).
You would instead need to import the Enterprise Reosurces to the plan,
rather than simply inserting the names.
Please let me know if I am mis-understanding your question.
-Bill
--
William Raymond [MS Project MVP]
(e-mail address removed)
BLOG:
http://www.mympa.org/blog.aspx
Hi,
I have a problem with resources. I open a Project from a Database, do
some
updates and close the project with publishing it. The problem we get is
that
the next time a project gets opened manually using MS Project, a
message
pops
up and says that the resources are not the Enterprise resources and
will
need
to be replaced. Or something along this line.
We tried different settngs for the openPool parameter. We are not sure
what
the parameter values actually do. Parameter Values can be
DoNotOpenPool
PoolAndSharers
ReadOnly
ReadWrite
nad Prompt.
Non of it made a difference.
I would be happy if someone would have an idea and is willing to share
this
idea with us.
Thank you very much in advance.
Cheers
Peter
