Circumventing a MSP Message

[Conrad Santiago]

I created a macro that publishes New and Changed Assignments on multiple
projects consecutively. The macro stops when this MSP message box comes up:

"There are no items to be published...."

1. Is there a way to OK this message when it comes up through a macro?

2. If not, is there a way to turn off these messages, so that they don't
come up?

As you can imagine, this is a pain, because I have to watch the macro run
and click <Enter> when the message pops up. For 100 projects, that's a half
hour vigil.

Thanks in advance for any responses.
--Conrad Santiago

 

[John]

I created a macro that publishes New and Changed Assignments on multiple
projects consecutively. The macro stops when this MSP message box comes up:

"There are no items to be published...."

1. Is there a way to OK this message when it comes up through a macro?

2. If not, is there a way to turn off these messages, so that they don't
come up?

As you can imagine, this is a pain, because I have to watch the macro run
and click <Enter> when the message pops up. For 100 projects, that's a half
hour vigil.

Thanks in advance for any responses.
--Conrad Santiago

Conrad,
There are several ways to handle this type of problem. I haven't dealt
with publishing so I don't know which approach may be best but here are
three possibilities. Try them in the order listed.
1. Try the DisplayAlerts property. Set it to False.
2. Use code to test for changes yourself so the message never pops up.
3. Try the SendKeys Statement

Hope this helps.
John
Project MVP

 

[Ed Morrison]

You can also check the UpdateNeeded property of the assignments, resources,
or tasks. If they are all false, you don't need to publish.

--
Ed Morrison
msProjectExperts
"We wrote the books on Project Server"
http://www.msprojectexperts.com
FAQ - http://www.projectserverexperts.com

 

[Conrad Santiago]

Great tips, guys!

I took John's advice and added the Application.DisplayAlerts = False to the
macro and it's working great!

If I use Ed's tip, I can probably cut the macro running time in half. Right
now, I have it so that it opens and saves each project regardless of whether
it needs the publishing or not. If I test the tasks first, I wouldn't need
to save.

Thanks, again!

--Conrad Santiago

 

[John]

Great tips, guys!

I took John's advice and added the Application.DisplayAlerts = False to the
macro and it's working great!

If I use Ed's tip, I can probably cut the macro running time in half. Right
now, I have it so that it opens and saves each project regardless of whether
it needs the publishing or not. If I test the tasks first, I wouldn't need
to save.

Thanks, again!

--Conrad Santiago

Conrad,
Great! I'm glad our advice was useful. And yes, a few ounces of checking
code can go a long way in making your macros more efficient and user
friendly.

John