I know there is or should be a way to use standard task codes for setting up timelines with successors and predecessors. Why would/should we have to use line numbers instead of task numbering. I am in a college class and we can't figure out how to do it. We enter the task number followed by the task or activity name. Then we enter the duration and the project start date. Next we go to the successors and have to assign the line numbers instead of the task numbers. This considerably complicates the thought process to substituting the line number from the task number making every job or at least jobs that vary in tasks a new exersize in numbering. There has to be a way to assign a custom numbering convention to be used this way.

Hello,

I'm afraid I don't quite follow your question.  The "line numbers" that you are referring to are the task IDs.  You do not have to type predecessor task IDs you can select the predecessor task and the successor task and use the Link task button.

There is a WBS Predecessor and WBS Successor field - but they are read only.

You also do not need to enter task numbers and activity names - add the WBS field to the view and the wbs numbers are there for you.

Try showing the Task form formatted to show Predecessors and Successors and see if that helps.

 

Yes, they are task ID's.
There has to be a way to assign custom ID's that can be utilized by the predecessor / successor macro.
I took a test this AM and we had to enter the CSI numbering as a task ID.
There has to be a way to get Project to use that convention.
It gets confusing when you have to convert the CSI ID's to Project ID's when you are under the gun.  

I don't believe the link relationships (predecessor/successors) are assigned through macros in Project.

However, Project can be manipulated through VBA.  If you have skills in that area, download the SDK from Microsoft's web site and see if you can create some code to assign using the custom ID field.

Julie

What is CSI numbering?

Could you give us an example of what MSProj does and then the same tasks with your desired approach.  You could probably get away with simply calling the tasks A, B, C, etc.. (no need for great detail) the IDs would, for MSProj, be 1, 2, 3, etc., and the successors (no need to show the predecessors since they would be logically obvious.  Try, too, to have something like this (with several levels of summary and detail tasks):

1 A
2   B
3     C
4     D
5   E
6     F
7 G

where A, B and E are summary tasks and C, D, F and G are detail tasks.  I didn't (as you can see) include the predecessor/successor relationships.

And, as Julie has said, predecessor/successor numbering (in fact, all task numbering) is handled by MSProj without any need for additional macros.

Here are the basic CSI categories:
DIVISION 1 GENERAL REQUIREMENTS
DIVISION 2 SITE CONSTRUCTION
DIVISION 3 CONCRETE
DIVISION 4 MASONRY
DIVISION 5 METALS
DIVISION 6 WOOD AND PLASTICS
DIVISION 7 THERMAL AND MOISTURE PROTECTION
DIVISION 8 DOORS AND WINDOWS
DIVISION 9 FINISHES
DIVISION 10 SPECIALTIES
DIVISION 11 EQUIPMENT
DIVISION 12 FURNISHINGS
DIVISION 13 SPECIAL CONSTRUCTION
DIVISION 14 CONVEYING SYSTEMS
DIVISION 15 MECHANICAL
DIVISION 16 ELECTRICAL
Each division can incorporate any number of special tasks as such:
Division 2 is site work so clearing can be 2000 and on up and so on.
2000 clear section IV Phase I
2100 drive piles section VI Phase I
2200 form caps section III Phase I
When these tasks are recorded in Project in order to timeline the job using successors or predecessors the line numbers need to be used instead of these task numbers.
This can lead to errors such as transposition or omissions and really gum things up.
I will know just how much tomorrow when (if) we get our tests back.
Using Excel you can avoid this by telling Excel which column or ineffect numbering convention to choose from.
There has to be an easy way to tell Project which numbering convention to use.
Mathematically speaking there should be no difference in the processing other than the range of numbers to use.
Project has a LOT of unused column headings or classifications that I had trouble with using because they either didn't accept the data I was entering or duplicated the data from another column needlessly.
With all the potential Project has as a relational database there has to be a way to do it.
If it can be done in Excel it can be done in Project.
Or should be anyway...

Sorry, I don't know what else to say, other than to invite you to look at the SDK and develop your own algorithm, if possible.

Project uses Tasks IDs in the predecessors and successors fields.  The alternative as I said is to link using the Task Form and select predecessors or successors by task names, not IDs.

Good luck.

 

So, using my example above, you want something like this (with the ID as the first data element and the task name as the second data element in each row):

ID   Task Name
==== =========
2000 A
2100   B
2110     C
2120     D
2200   E
2210     F
3000 G

Ain't gonna happen.

The ID field is dynamic and begins at 1 with increments of 1.

The Predecessor and Successor fields *must* refer to the ID field values.

You could use one of the Number fields and write a macro to display the values you want but it would be a nontrivial piece of code that would have to handle insertions and deletions as well as drag-and-drop resequencing (and that's just for starters).

While you are *somewhat* correct that Project is a relational database, the schema is deliberately not fully documented and there are some very complex relationships behind the scenes (especially when it comes to TimeScaleData which is a multi-dimensional form of a sparse matrix).
 

I am beginning to accept that as truth.
I upgraded to Project 2010 thinking there would be more features I need.
I like the scrolling menu's, makes quick work of choosing a column.
Tried Unique and WBS ID choices with the same results.
Why would there be those choices when they act the exact same way?
JulieInMaine had it right, create a macro in VB.
I am blown away that a high priced program can overlook a feature as simple as this.
Reckon that is why they have updates (to sell).
Maybe some day they will let it out.
Thank you all for your support.

To be truthful, you are the first person in the years that I have worked with Project and visited forums to have ever asked for this utility.  Most people I know want the ability to create predecessors and successors by name, not ID.  That facility does exist.

 

That would work also.
Anything except line numbers.
How is this accomplished?
 

I found WBS Predecessors & Successors.
Unique ID Pred & Suc.
Both appear to work the exact same way as original does so what is the point?
Anything is better than line numbers.
I installed VB.
Quite a daunting program.
Any shortcuts I should know to get the job done?

As i noted in my first reply, the WBS Predecessor and Successor field is read-only.  You cannot use it for assignment.

The Task Form (Window Split from a Task view) formatted to show predecessors and successors lets you select tasks by name as either the predecessors and successor.

You should not need to install VB - project uses VBA.  Press       ALT + F11 to invoke the VBA Editor while in Project.

 

Yes but there is a WBS column as well as a Unique ID column.
Each can be assigned custom numbering.
Both are followed by their namesake predecessors and successors.
No way can either be used to schedule, only read only as you said.
I am looking into the Task Form you describe to use the naming convention.
That has to be more convenient than line numbers.
I got the Task Form open but I don't see how to do it except for the previous and next buttons that scroll through the list.
Is there another thread I can peruse rather than you walking me through it all over again?
Not that I mind, I don't want you to waste you time.
I don't have anything better to do.
I go to school full time.
Hopefully, there will be a job before I graduate...

You wrote:
Yes but there is a WBS column as well as a Unique ID column.
Each can be assigned custom numbering.

No, only the WBS field can be assigned a custom number scheme.  The UniqueID field is read-only and is used internally by Project in the case of tasks being moved, inserted, or deleted.

You wrote:
I am looking into the Task Form you describe to use the naming convention.
That has to be more convenient than line numbers.
I got the Task Form open but I don't see how to do it except for the previous and next buttons that scroll through the list.

Click under the word "Precedessor" in the task form and select the task name.  Then click OK.  Select the next task you wish to assign predecessors to and so on.

Project is not an intuitive program and if possible, you should take a good 2+ day hands-on course to understand how the product functions.  Is that not part of your classes at school or are they just throwing you into the deep end and asking you to use project without any instruction in how the product works?

Yes, you are right, the Unique ID column can't be modified.
There are limitations to the book we are using.
Me being me, I have to try to  figure out what I would think makes things easier for me. What features I would expect for my money.
Duration and Actual Duration once Progress is 100% always end up the same.
To keep an estimated duration from defaulting to the actual duration you have to use Baseline Duration of which there are ten of.
I am just making sense of this program to make my job easier.
We have also used Excel, which while rudimentary in it's interface can be programed where Project as you can see I am having a little difficulty with.
I have a little experience with relational databases, enough to know that it can be done and not enough to know exactly how to do it.
Once you (we) implement a numbering convention what is the point if each schedule we have to redo it?
It is simple numbering either with line numbers or task numbers.
IF, THEN, ELSE.
I took a semester of programing and it is not that hard.
You just have to know the interface to get what you want out of it.
That, I am still working on...