B
BobS
We are running a MS Project Database (MPD) with a twenty or so small projects
stored within, each of which are inserted into a master project file also
located within the same Database.
The whole database file has developed thru several generations, ( A
generation occurs when we have saved the database to a new name)…….the
problem that arises is ensuring the actual location of the data of the
inserted projects …and avoiding unintentional changes to source data.
I am now trying to ensure we keep track of the inserted files ( they do not
follow the saved out database)…..so I need to be sure I can get the
individual projects back into the master database file. What is the best
form of managing this?
Opening the Projects Table in Access indicates a data source path……….but
this does not match the locations indicated in the Gant view or
source.......which correct ? and what happens if you need to move the
database ?
stored within, each of which are inserted into a master project file also
located within the same Database.
The whole database file has developed thru several generations, ( A
generation occurs when we have saved the database to a new name)…….the
problem that arises is ensuring the actual location of the data of the
inserted projects …and avoiding unintentional changes to source data.
I am now trying to ensure we keep track of the inserted files ( they do not
follow the saved out database)…..so I need to be sure I can get the
individual projects back into the master database file. What is the best
form of managing this?
Opening the Projects Table in Access indicates a data source path……….but
this does not match the locations indicated in the Gant view or
source.......which correct ? and what happens if you need to move the
database ?