Using a temp DBC is fine. What I was after is for you to create your DBC as you normally would in your App as well as any views including the problematic one. Then run GENDBC against this temp DBC. This will generate all the code that would be needed to recreate your DBC and all its contained objects. Then copy and paste the complete set of code for the view only from that generated PRG file here.

For me at least, that would make it easier to spot a problem with setting up the view properties.

>I should have asked in the other posting... what other coding would you require?
>
>I use a custom view object which creates the view and applies the appropriate properties to enable updating. This view has been in use for about 4 to 5 years. I assume that it has never had to deal with a LEFT OUTER JOIN before. I don't need the description table to be updated just the source table; but it still needs the fields to be included in the updatefieldlist and tables properties of the cursor.