Set Flag = Yes for Project Summary Task

[VSAT Ryan]

Hi-

I need to set flag2 = Yes for the Project Summary task without setting flag2
= yes for any of the other tasks. I would prefer if users didn't have to do
this on their own. I originally tried setting the default value = yes for
the flag2 column, but this makes flag2 = yes for all tasks.

Please help!

Thanks.

 

[John]

Hi-

I need to set flag2 = Yes for the Project Summary task without setting flag2
= yes for any of the other tasks. I would prefer if users didn't have to do
this on their own. I originally tried setting the default value = yes for
the flag2 column, but this makes flag2 = yes for all tasks.

Please help!

Thanks.

VSAT Ryan,
Well there are various approaches. One is to create a template file with
flag2 of the Project Summary Task set and then have all you users create
their files from that template. Another is to create an Open Event macro
that sets the Project Summary Task flag whenever the file is open. The
third is of course to have the users set the flag themselves. It all
depends on what level you want to go to to get the flag set.

John
Project MVP

 

[VSAT Ryan]

Hi John-

Thanks for the responses, but I should have been more clear.

We are using software that generates a new MSP file every time a user needs
to access the data. Ultimately, each MSP file will only be used for a few
days at a time, rather than for weeks or months.

Since a new MSP file generated every time, I was looking for something to be
set in their global.mpt file. An open event macro might work if it could be
triggered every time any new MSP file is opened.

Any suggestions?

Thanks again,
Ryan

 

[VSAT Ryan]

Thanks Trevor, but unfortunately, the other software system we are using with
MSP calls a function that every time a new task is created, flag2 is set to
Yes (which creating a new task has nothing to do with the flag2 = Yes at the
project summary level).

Ryan

 

[John]

Hi John-

Thanks for the responses, but I should have been more clear.

We are using software that generates a new MSP file every time a user needs
to access the data. Ultimately, each MSP file will only be used for a few
days at a time, rather than for weeks or months.

Since a new MSP file generated every time, I was looking for something to be
set in their global.mpt file. An open event macro might work if it could be
triggered every time any new MSP file is opened.

Any suggestions?

Thanks again,
Ryan

Ryan,
Yes more information is always better. You are using Project in a rather
unusual way.

If another application creates a new Project file, why not have that
application set the flag? If for some reason that isn't viable, then the
Open Event suggestion will probably work but it depends on how the new
Project file is created. In one sentence you say a new Project file is
"generated", implying it is being created but from what we don't know
(e.g. import from Excel, a database, etc.). However, in another sentence
you say a new Project file is "opened", implying the file already
exists. Those may seem like fine points, but I afraid your "expanded"
explanation generated more questions.

John
Project MVP

 

[VSAT Ryan]

Ok, here is the deal.

We are using Oracle Project Management, which has a MSP interface. The data
flow is bi-directional, so the user can "download" (ie. generate a MSP file)
from oracle, make changes, and send data back to Oracle.

Oracle uses the flag2 column at the project summary level as a setting I
need all users to be at Yes. The default is no. Oracle also uses flag2 at
the detailed task level for a completely different function. The entire
interface is built off of VBA. Making any modifications to their code is
obviously not supported.

I chose to use this forum first rather than going to Oracle since it will
take too long to get an answer out of them.

Thanks,
Ryan

 

[John]

Ok, here is the deal.

We are using Oracle Project Management, which has a MSP interface. The data
flow is bi-directional, so the user can "download" (ie. generate a MSP file)
from oracle, make changes, and send data back to Oracle.

Oracle uses the flag2 column at the project summary level as a setting I
need all users to be at Yes. The default is no. Oracle also uses flag2 at
the detailed task level for a completely different function. The entire
interface is built off of VBA. Making any modifications to their code is
obviously not supported.

I chose to use this forum first rather than going to Oracle since it will
take too long to get an answer out of them.

Thanks,
Ryan

Ryan,
Well, you're into an area where I have absolutely no knowledge although
some of my fellow MVPs may. I suggest you post to our developer
newsgroup at, microsoft.public.project.developer. I won't guarantee
you'll get an answer but you might get lucky. Do you feel lucky? Well,
do ya?

One small detail about your post. You say the interface is built using
VBA. My guess is you really mean VB. Visual Basic for Applications (VBA)
is a version of Visual Basic that is run from within an application. It
(VBA) does not exist as a stand alone entity whereas VB does (e.g. VB6,
VB.net). I guess it's possible the Oracle Project Management application
includes VBA. In that case your statement about the interface being a
VBA procedure, is correct.

John
Project MVP