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.

>Mark,
>
>This brings up another question. I have asked about whether its better to have
>a single generic CA for an app, or one for every table. If you go with one for
>every table, how do you deal with JOIN's?
>
>Thanks