Import af hierarkidata

Your going to have to make your own import routine. Strat by importing into a TEMP table and then open a recordset where you loop through all records.

Can you explain your data a bit more, as I'm not sure if its neceesary to have more than one table?

Jeg lavede engang en funktion, som skulle lave noget lignende, hvor der skulle stå én værdi i felt1 og en tekststreng i felt2. Du kan evt bruge den som inspiration:

    Do Until RS.EOF
         
        StrValue = RS.Fields(0).Value ' Værdi til Felt1
        strListOfValues = "<b>" & RS.Fields(0).Value & " " & RS.Fields(1).Value & "</b>" ' Startværdi til Felt2
        RS.MoveNext
       
        'Indre løkke. Opbygger tekststrengen til Felt2
        While Not Mid(RS.Fields(1), 5, 1) = "" ' Bliv ved til der kommer en post med kun fire tegn i Felt2
            strListOfValues = strListOfValues & "<br><br>" & RS.Fields(0).Value & " " & RS.Fields(1).Value ' Tilføj værdier til Felt2-strengen
            RS.MoveNext
        Wend
       
        'Make sure there is something to write
        If Len(strListOfValues) > 0 Then
            'Tilføj post til Tabel1
            With Rst
                .AddNew
                !felt1 = StrValue
                !felt2 = strListOfValues
                .Update
            End With
           
        End If
       
    Loop

Jeg har overvejet, om ikke TreeView-funktionen ville være velegnet til formålet. Har I nogle erfaringer med automatisk dataload af hierarkier til denne ????

Umiddelbart vurderet er det netop via NodeID og ParrentID jeg kan sikre de korrekte summeringer i hierarkiet.  TreeView-funktionen skulle så styre strukturen, og data ligge på kontoniveau.

Jeg kunne selvfølgelig oprette strukturen manuelt i TreeView, men der er p.t. tale om 1800 poster i hierarkiet ... ydermere ændrer hierarkiet sig løbende, så et dataload er at foretrække.

Nogle gode ideer ????

A treeview would be a goode idea, but still you need to do it  in code to make sure that the structure is correct. (Which lines in the file are related). So if you can get it in one or more table sthen you can also get it in a treeview.

Terry > Can I send you a file with the structure ... maybe you can figure it out ?

Yes, send me the file, but I'm pushed for time right now, so you may have to wait for an answer.

Can you also explain the data?


You say "Al dataregistrering foregår på kontoniveau ( nummerisk ) pr. måned."

But I dont see any month or ammount to sum.

Anyay tell me what you can and I'll take a look.

Mail ?

What you see, is just the "stamdata"-hierarki ... data is located in a different table with this :

KontoNr    Jan        Feb      ....
70001      125.000    120.000  ....
70002      130.000    110.000  ....

eksperten@NOSPAMsanthell.dk
remove NOSPAM

I'm sure I will have some question after I have seen it.

Can you send me the other table too

I've now had a very quick look at the data and before it can be used for anything at all then it will be necessary to decide what you need from kontohierarki. For example you could just tak ethose starting with a number and make this the konto number, and the remaining text konto text.
For example:

70141 JETPOST NAT REF

would be in tblKont with two fields (kontonr, and kontotekst

Then it woul dbe very easy to have a relationship from that table to the data table on field KontoNr.

I am aware of that ... thats not the issue ... kontonr, and kontotekst is in another "stamdata" table. I only need kontonr in the hierarki-table ...

I need a method/module to determine the right nodeId and parrentId in the TreeView. Notice, that kontonr can be found in different levels of the hierarki ( level 2, 3 , 4 and so on )

You have to realise that I have very little knowledge of your data and your reuqirement. Having the full picture does simplify things.

At the moment I dont have the examples you sent me, so cant refer to them. But I remmeber that there was no really difined structure in the hierarki table. The only thing was the lines which contained a kont number/texts. Thus is why I said that you should decide what you need from the table.

Anyway if we take your example above then a method woud be to loop through the records giving each record a parent node when it gets inserted into the final table. This requires some method of recognising when your at the top level and when you change to a lower level. But as I mentioned, there doesnt seem to be a defined structure, so this isnt going to be easy.

Example:

TopNodeName, IsKontoNr, NodeName, NodeText, ChildNodeID, ParentNodeID
R, 0,R, Result, 1, 0
R, 0,R1A, Dækningsbidrag, 2, 1
R, 0,R1A1, Omsætning, 3, 2
R, 0,R1A1A, Pakker Indland, 4, 3
R, 1,70001, Pakketype 1, 5, 4
R, 1,70002, Pakketype 2, 6, 4
R, 1,70003, Pakketype 3, 7, 4
R, 0,R1A1B, Pakker udland, 8, 3
R, 1,70002, Pakketype 9, 2, 8
R, 1,70002, Pakketype 10, 2, 8


From the above example I can always build a tree placing each node at the correct level. I can always find which nodes are related and also which records contain the actual konto number.

Hi Terry

I´ve used all night to make the NodeID and ParrentID "hånd-line" ( manually )

I hope you can se what I will achieve ;o)

Access-database sent

I'll take a look as soon as I get a bit of time

There´s no hurry ...

Hi Terry ...

There´s no need to make a solution, I´ve found a work-around method. Actually I´ve found out, that my data-source could do the work for me/us ... but thank´s anyway.

Place an answer, and get som point´s

I had a look at your dB you sent, still wasnt sure what you wanted.

Don´t worry ... I´m not sure either ;o)

Now I have generated the hierarki, placed data on kontonr-level ... and then what !!

Now I have to figure out the calculation within the hierarki