Global field behavior change 2002->2003

A

Albert Gardner

Hi there,

I have an issue that may require a VBA macro as a
solution, but I would like to avoid that if possible. I
have a master project that contains 400 or so subprojects.
in each task of these sub projects, there is custom text
field that is a restricted value list. In project 2002, I
could add new values to the list in the master project,
and copy it to the global, and change the values of the
custom field (all inside the master project). In project
2003, I can add / change a value in the list, copy it to
the global, but I cannot access the new value in any
subprojects, they retain their own specific value list
from their linked files. I can write a macro that runs
through the subprojects, opens each file, copies the
global field to their own field, then saves the file...
but I would rather do it the old way I did in 2002,
because there are other files that use the global fields
that are not linked to the master file that I would like
the changes to effect also.


Thank you for your thoughts and time,
-Albert Gardner
Production coordinator
DR Horton - Seattle Division
(e-mail address removed)
 

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