Guild of Project Controls: Compendium | Roles | Assessment | Certifications | Membership

Tips on using this forum..

(1) Explain your problem, don't simply post "This isn't working". What were you doing when you faced the problem? What have you tried to resolve - did you look for a solution using "Search" ? Has it happened just once or several times?

(2) It's also good to get feedback when a solution is found, return to the original post to explain how it was resolved so that more people can also use the results.

Retaining Activity ID logic

3 replies [Last post]
John Pease
User offline. Last seen 3 years 37 weeks ago. Offline
Joined: 4 Mar 2016
Posts: 3
Groups: None

I need some help please. I have two seperate schedules linked together by activity ID's, but on a monthly basis I will need to update and produce copy files and re-write the links because they are not retainied. The Project ID changes but not the Activity ID remains the same.

 

This is obvioulsy time consuming, and because the schedules are updated they will be individually different files. So the question is can you retain the links between schedules even if they may have different data date etc. or different copies but still retain the same activity ID logic.

Replies

Zoltan Palffy
User offline. Last seen 3 days 12 hours ago. Offline
Joined: 13 Jul 2009
Posts: 3089
Groups: None

that certainly would help to have the database in a centralized location

John Pease
User offline. Last seen 3 years 37 weeks ago. Offline
Joined: 4 Mar 2016
Posts: 3
Groups: None

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

Zoltan Palffy
User offline. Last seen 3 days 12 hours ago. Offline
Joined: 13 Jul 2009
Posts: 3089
Groups: None

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.