>I have a generic CA in my CA class library that I then subclass each time I have a special need like that. If it purely for lookup (read-only) purposes, I use SPT instead. When I am updating data, I generally am using 1 CA per table anyway. I can't think of the last time I had an updatable view comprised of multiple tables.
>
>I am also looking at modifying my builder to work with free tables. The problem would be determining the PK field(s) since that does not exist with free tables. About all I could offer would be if there was a candidate field identified.
I would expect this type of automatic generation to tell me: "Table doesn't have a primary key - please select key field(s) from the following list: ..." It might suggest the first field in the table (1), but let the user select another field or fields.
(1) I always use the first field in the table as the PK, but I don't know how common this practice is.
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)
