Many to many relation. How?

[Robert Brenstein]

>>If you delete, then your ids are not serialized (as in newer not 
>>always having a higher number) but you probably timestamp them 
>>anyway. So if you do not have the requirement that they keep always 
>>increasing, then you can still use the built-in recId as id.
>>
>>Robert
>
>Hm, not bad. But won't a much longer string decrease speed of queries?
>The best solution would be an integer, wouldn't it? But then the 
>database could run out anytime.
>Or do you think of a relation based on more than 2 fields?
>
>
>Cheers,
>Ralf

RecId is an integer. So is (at least can be) the timestamp. I would 
not be concerned about the speed decrease related to having a tad 
longer query string. The network performance will remain the 
bottleneck IMHO.

Robert