Any of the SQL view operations require a key to work correctly.

>Hi all,
>
> I've not done this before and could/should experiment to get my answer but thought someone here might have had this experience...
>
> I'm considering building updateable Views into the tables of an old pre-existing app. I find that some of the old tables weren't designed to have any unique keys. This would seem to be a problem for the View's Key requirements when it performs an SQL update. Is this true? Would the 'Update using' options of "SQL DELETE then INSERT" versus "SQL UPDATE" make a difference in this case?
>
>Thanks,
>Steven-