>Are there any reason to use or not use the AutoIncrement feature
>of the table designer? I could use a custom procedure to add primary
>keys.
My opinion - and for now, not of much more value than a simple opinion - is that, if you already have a function for sequences, use this old-fashioned way (you can call it up from the field's default value). I think you will have more control over the details. For instance, I think I read that it is tricky to reset a sequence to zero after ZAPping a table (not that it really matters, if you use PKs without business value).
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)
