Many to many relation. How?

[Ralf Sander]

On 06.12.2004, at 15:38, Robert Brenstein wrote:

>>  >
>>>  Ah, I did not realize that you are talking client-server. A 
>>> variation
>>>  of this can still work but details would depend on your specific
>>>  situation. If your serialization is only to get unique identication,
>>>  then you could use the recId values that Valentina assigns
>>>  automatically. If your records are not deleted, these would actually
>>>  be serial numbers.
>>>
>>>  Robert
>>
>> Unfortunately, records will be delete. So I need ids.
>>
>> Cheers,
>> Ralf
>
> 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