Publish multiple projects from a store procedure

[andrea]

Greetings
I'm trying to do a bulk update of some custom enterprise fields in
MSP_TEXT_FIELDS with a store procedure. Everything's fine, if I open
Project Pro I see my changes in the custom fields.
The (known) problem is that, in Web Access, I see nothing or the old
value: of course, I have to open the project in PrjPRO, publish the
project, and after the updated field will be visible in Web Access.
My problem is that I have more then 14.000 projects to update, so
opening each project manually this is not the best option....Is there
any single store procedure to be called, to pass the Proj_id, and it
publishes the project? So simple it seems....
Thanks in advance for any suggestion
Andrea

 

[Gary L. Chefetz [MVP]]

Adrea:

Using 2003, you need to either automate around Winproj, or automate the
process by creating your own XML packages in the ViewDrop to get the system
to do its thing. The latter is probably the easiest approach, and I trust
that you have multiple instances of the notification service running to
handle this many sequential jobs in an overnight batch.

 

[Gary L. Chefetz [MVP]]

One other thing.. Are you planning on upgrading to 2007 in the near future.
If so, I'd look at using the PSI.

 

[avfdmavfdm]

Thank you Gary, but I'm not planning to upgrade. Imagine that I'm
thinking to create a VB6 application, using the MSProject object, open
first project, publish, open second project, publish.....:-(
Is there any quick way using PDS?
Andrea

Gary L. Chefetz [MVP] ha scritto:

 

[Rod Gill]

PDS is not worth investing time as it is not supported in the new 2007
version. A simple macro in Project VBA will run quicker than a VB or C#
code. It should read all projects from the database, then open each in turn,
publish it then close.

Try recording a macro of you manually opening then publishing one project
then wrap a loop around that code and the oledb code needed to read all
project titles and you're done!!

It's actually one of the sample macros in my book, but as you're a VB6
developer the above details should be enough for you!

--

Rod Gill
Project MVP

NEW!! Project VBA Book, for details visit: http://www.projectvbabook.com

 

[avfdmavfdm]

thank you Rod
I look with sql profiler at what Project Pro does when we select
"publish", I think that MS should provide one unique functionality in
the data layer. I was hoping to have a cleaner and more
performance-oriented solution, i.e., passing through stored procedure.
Do you think that, if I wrote this SP, it could be published in your
next book ? It's incredible that for this functionality, we have to
pass from VBA.
Anyway, thank you for your support,
Andrea


Rod Gill ha scritto:

 

[Rod Gill]

I'm not sure an SP will suffice as Project often stores some critical
information in binary blobs which would be next to impossible to do with an
SP, so don't spend too long on it!

Certainly when the current batch of books sells out, we will update it
before doing another print run, so if it is possible to publish just from an
SP, I will happily publish it!

--

Rod Gill
Project MVP

NEW!! Project VBA Book, for details visit: http://www.projectvbabook.com