File output Seq 1

[gertNo1]

Hi Guys,
I was under the impression that if you do not have a key on a table the order in which the table was written would be maintained.

I created a table that requires headers for each group of account numbers. The hdr is based on the 1st 8 bytes of the account number.
e.g.
9991803 9 00 xxx xxxx xxxx
999180329642222 099 01 j10 yyyyddmm xxxx
999180329642238 099 01 j10 yyyyddmm xxxx
999180329642265 099 01 j10 yyyyddmm xxxx
9991910 9 00 xxx xxxx xxxx
999191029642222 099 01 j10 yyyyddmm xxxx
999191029642238 099 01 j10 yyyyddmm xxxx
999191029642265 099 01 j10 yyyyddmm xxxx

The table my program creates is perfect, the account number field on the output table is keyed. When I append the records to a new table (account number is not keyed) the records do not maintain their original order. The file my program inputs is keyed on account number. Why am I loosing the order in which the file was read and written?

FYI, I put the 1st eight bytes on the hdr to maintain order and verify the data. Before I export to the User I must remove the 1st eight bytes on the hdr. Thus the final output cannot have a keyed account number field.

Thanx

 

[gertNo1]

I'm sorry, I should have said the account number field is Indexed not Keyed

Thanx

 

[dhookom]

I have always considered records in an Access table to be un-ordered. Much like marbles in a bag. If you want to put them in order, you need to have a value stored in a field or fields that describes the order.

Duane MS Access MVP
Now help me support United Cerebral Palsy

 

[lespaul]

I love your "marbles in a bag" example.....

les

 

[dhookom]

Depending on my mood, I will also use "chidren on a school playground".

Duane MS Access MVP
Now help me support United Cerebral Palsy

 

[gertNo1]

Thanx so much dhookum for responding, I too loved your analogy and agree with it although it didn't help my cause much.

Oh, well I'll have to find another way.