In article <946855CC-918D-4B73-92C4-742A90082B96@microsoft.com>,
My comments are in-line
Well, it can't be independent of the view since as I stated previously,
all "select" methods refer to the current active view. And to highlight
something in Project, (using VBA), you have to use a select method -
unless the field cell has already been selected from a previous action.
This is one area where Excel "excels" over Project - In Excel, cell font
characteristics can be set using background processing.
This is easy for background processing. For example to set the duration
of Unique ID 6 to 10 days, the following statement is all that is needed:
ActiveProject.Tasks.UniqueID(6).Duration = 4800
Note that duration is expressed in minutes and for a normal work day,
there are 480 minutes in a day.
There are various ways to do this.
One method I use all the time when I'm troubleshooting code I'm writing
is to display the VB editor as a small window over the file I'm working
with (Project or Excel). I either set up breakpoints in the code, (a
Stop statement also works nicely for a more permanent breakpoint), or
step through it to the code line of interest. I then activate the
application window to view/analyze the result. When I want to go on, I
activate the VB editor window again and step or run to the next
breakpoint. This method works great but you may find it a bit cumbersome
in a presentation scenario - it depends on the audience.
Another way to do this is with a userform just like you do in Excel.
Although I've never used an interactive userform (where control passes
from userform to application and back at prescribed points), the setup
for Project should be the same.
A final thought. For the last program I worked on, we had a monthly
program review day. Each cost account manager (CAM) walked through their
status (both technical and formal earned value) in a group meeting with
other CAMs, the program manager, a customer representative, our program
business office and other interested parties. Prior to the meeting, I
made a consolidated master file of all CAM files. I also had a couple of
macros that I could use to delineate certain characteristics of the CAM
file (e.g. 30-day look-ahead, probability of cost or schedule variance
given the current trend, etc.). We did not change any file data during
the meeting, (doing so required a formal change request document), but
we could manually highlight any fields of interest during the discussion
either by selecting the field cell or with a laser pointer. Data errors
that were discovered were noted in the meeting minutes so they could be
addressed after the meeting.
Hope this helps.