>>On the other hand, relationships between tables will be a lot simpler if you store the Primary key in a single field.
>
>I may be biased, but I like working with composite keys. In your example, how do you established the foreign keys once you have merged two fields into one ?
Just as with a composite key: with the REPLACE command. With a single field, you need a single REPLACE command instead of two.
>But I am very happy with your BINTOC solution, which according to my test indeed preserves the order.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
