Thank you. I thought I would ask the question and I think the only way forward is to use a single database that external parties have access to, such as a Loadspring. As each file is external and issued from and external source the Project ID differs each issue. I was not sure if there was a new way of tackliing this. Cheers
Member for
16 years 3 months
Member for16 years3 months
Submitted by Zoltan Palffy on Fri, 2018-08-17 14:09
why dont you just continue to use the same schedule this way the project id and activit ids stay the same. Whne you are done with you update copy that project and save it as the update for the month or period. Then you have your historical schedule data if you need it.
Member for
16 years 3 monthsthat certainly would help to
that certainly would help to have the database in a centralized location
Member for
9 years 8 monthsThank you. I thought I would
Thank you. I thought I would ask the question and I think the only way forward is to use a single database that external parties have access to, such as a Loadspring. As each file is external and issued from and external source the Project ID differs each issue. I was not sure if there was a new way of tackliing this. Cheers
Member for
16 years 3 monthswhy dont you just continue to
why dont you just continue to use the same schedule this way the project id and activit ids stay the same. Whne you are done with you update copy that project and save it as the update for the month or period. Then you have your historical schedule data if you need it.