WBS sequence not kept on Import

I have a table that is defined by our ERP system and use a macro to pull the
information in from a SQL table via ODBC using an import map. The problem is
that if I look at the SQL table the WBS codes are in sequence but when they
are pulled into Project this seqence is jumbled and resorting on WBS code
does not seem to fix it.

For Example by codes in the SQL table read.
1
1.1
1.1.1
1.1.2
1.1.3
1.1.4
1.2
1.2.1
1.2.2
1.2.3
1.2.4

However when imported they come out as

1
1.1
1.1.1
1.1.3
1.2.2
1.2.3
1.2
1.2.1
1.1.2
1.1.4
1.2.4

which totally mucks up the tasks and sub tasks
Ant ideas ?

Gérard
Fri May 13 01:31:24 CDT 2005

Hello,
Instead of the WBS code, try to import the Outline Level field

Gérard Ducouret

"Nickb" <Nickb@discussions.microsoft.com> a écrit dans le message de
news:0012AC0A-8C53-4BC2-90C2-EA7DDF33AEBE@microsoft.com...
> I have a table that is defined by our ERP system and use a macro to pull
the
> information in from a SQL table via ODBC using an import map. The problem
is
> that if I look at the SQL table the WBS codes are in sequence but when
they
> are pulled into Project this seqence is jumbled and resorting on WBS code
> does not seem to fix it.
>
> For Example by codes in the SQL table read.
> 1
> 1.1
> 1.1.1
> 1.1.2
> 1.1.3
> 1.1.4
> 1.2
> 1.2.1
> 1.2.2
> 1.2.3
> 1.2.4
>
> However when imported they come out as
>
> 1
> 1.1
> 1.1.1
> 1.1.3
> 1.2.2
> 1.2.3
> 1.2
> 1.2.1
> 1.1.2
> 1.1.4
> 1.2.4
>
> which totally mucks up the tasks and sub tasks
> Ant ideas ?

Nickb
Sun May 15 19:26:02 CDT 2005

Gérard Thanks for quick response. However this does not seem to work either.

the structure I am after is like this.

A
B
C
C
C
B
C
C
C

where the B's are subtasks of A and the C's are sub tasks of the B's
to acheive this I have set as suggested the outline levels

1
2
3
3
3
2
3
3
3

The problem is that some tasks at the level 3 get jumbled up into the
different level 2's. I have checked the source table and they are stored in
the correct sequence there and if read sequentually or through the default
index they should be read in correctly.

Do I need to change my Outline level somehow or some how force MS Project to
use the default table index ?

Thanks






"Gérard Ducouret" wrote:

> Hello,
> Instead of the WBS code, try to import the Outline Level field
>
> Gérard Ducouret
>
> "Nickb" <Nickb@discussions.microsoft.com> a écrit dans le message de
> news:0012AC0A-8C53-4BC2-90C2-EA7DDF33AEBE@microsoft.com...
> > I have a table that is defined by our ERP system and use a macro to pull
> the
> > information in from a SQL table via ODBC using an import map. The problem
> is
> > that if I look at the SQL table the WBS codes are in sequence but when
> they
> > are pulled into Project this seqence is jumbled and resorting on WBS code
> > does not seem to fix it.
> >
> > For Example by codes in the SQL table read.
> > 1
> > 1.1
> > 1.1.1
> > 1.1.2
> > 1.1.3
> > 1.1.4
> > 1.2
> > 1.2.1
> > 1.2.2
> > 1.2.3
> > 1.2.4
> >
> > However when imported they come out as
> >
> > 1
> > 1.1
> > 1.1.1
> > 1.1.3
> > 1.2.2
> > 1.2.3
> > 1.2
> > 1.2.1
> > 1.1.2
> > 1.1.4
> > 1.2.4
> >
> > which totally mucks up the tasks and sub tasks
> > Ant ideas ?
>
>
>