...
>I've got several Local Views which I am using as prototypes until my client can fork over the dough to upgrade to a real server. Anyhow, I have paramterized all of these views and am allowing updates. A primary key (or keys) have been identified for each view. In order to add records to the base table I am bypassing the view and issuing a direct SQL insert into the table. (IF I simply add records to the view, the SQL update doesn't populate the key fields for me.)
>Question #1: Is there a better way to do this?
>Question #2: Will this work when these tables become remote?
...
I am not sure about Oracle (that's in case you client will be will be willing to spend THAT much on the "real server"), but on SyBase and MSSQL servers you can use IDENTITY instead of PRIMARY KEY. First, the uniquness is guaranteed, second, - you won't have to worry about inserting the value into it (in fact, you can't unless you explicitly SET IDENTITY_INSERT ON for the table)...Just a thought :)

Good luck.