Carrying Info between Sessions

[RobV]

I have a VBA macro that analyzes a schedule. I'd like to carry the results
of the analysis from one session to another. I've thought about plugging the
data into unused custom fields or into the Notes field of a dummy task, but
that's what engineers call a "kluge". Does anyone have a better approach?

 

[BillB]

What type of info do you want to carry over? Is it attached to the project?
Look into Project Custom Document properties. You can create and read custom
fields attached to the project record that store text, date, number, or
yes/no values.

Bill B

 

[Rod Gill]

There is nothing wrong with using custom fields for data. If its a small
amount of data save it in the registry using SaveSetting and GetSetting
commands.

For a large amount of data I would save it to a text file with the same name
as the project file (save the full path in a custom text field in case the
PM renames or moves the project).

--

Rod Gill
Project MVP

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

NEW!! Web based VBA training course delivered by me. For details visit:
http://projectservertraining.com/learning/index.aspx

 

[Jan De Messemaeker]

I often put such data in the global.mpt where they can be accessed from
every project.
vbe.vbprojects(1).vbcomponents(1).properties("Text1")=...
for instance

--
Jan De Messemaeker
Microsoft Project Most Valuable Professional
+32 495 300 620
For availability check:
http://users.online.be/prom-ade/Calendar.pdf

 

[RobV]

Thanks, everybody, for the ideas.

I often put such data in the global.mpt where they can be accessed from
every project.
vbe.vbprojects(1).vbcomponents(1).properties("Text1")=...
for instance

--
Jan De Messemaeker
Microsoft Project Most Valuable Professional
+32 495 300 620
For availability check:
http://users.online.be/prom-ade/Calendar.pdf