Between the 2 of you i am going to figure this out. <vbg>

well that is starting to make sense now!
VERY simple and deffenetly not programmer worthy spoken, you could compare this process with the sorting of the start menu in windows.

the 'programs' in the start menu are only short cuts (links to the data of the sql table). when i sort the start menu, all i realy do is rearange the shortcuts on the hd rather then rewriting and moving araund the actual program file.

Now that makes sense!

BUT, why can i not have more then 1 clustered index then? semse to me, that i could have multible 'columns' with shortcuts?! ergo: have multible clustered indexes.

>Gunnar,
>
>What Jim said is not even close to how the clustered index internaly works. All clustered index pages lniked into double linked list. That what creates "Physical order". To add a record in the middle of the clustered index SQL Server has only to change links in that list. The page with index and data can be located anywhere.
>
>>thank you Jim
>>
>>ja, doesn't sound like anythink i would want to use.
>>
>>>Well I'd consider it more akin to the old "INSERT" (not the INSERT - SQL) command of VFP with the difference that in the case of SQL Server it does leave some empty spots throughout the table in anticipation of new records coming in sooner or later.
>>>
>>>[The old INSERT command actually inserts the record into the specific place that you told it to, recopying the old records after the new one to make room for it. Not a great technique, speed-wise.]