You should treat deleted records as none-existent, the same way as it would be on SQL Server back end. You should use your own flag to mark records as deleted.

>One of the things that you cannot seemingly pass on is the Marked for Deletion marker when you combine a couple tables into an update-able Local View. I suppose that there is most likely no way around this?
>
>SUB-POINT:
>I gave up on using the data environment to open my Local View, because I kept getting an error message stating:
>

"Error in instantiating cursor object"

>This error continued to occur no matter that I had opened the database in the main program, or set database to the DBC name, or set path to the dbc. Nothing made a difference, so I am explicitly opening my tables and the one Local View. With the local view, I made it Optimistic Buffering with the command:

CURSORSETPROP("Buffering", 5, "lv_Orders")

>The Local View JOINS the ORDERS and CUSTOMERS tables. I do NOT update the Customers table, only the ORDERS table. There is a button for the user to either select from a table of Customers or to add a new customer record. The ORDERS form shows the last name and first name of the Customer's name; those text boxes are disabled.
>
>MAIN POINT:
>With a regular table (not a View), I show a RED text message that simply states "DELETED" as the user navigates through the table. However, as I just noticed that this is not "propagated" (carried on) on through to the Local View, I find myself wondering how to let the user know that a record in the main table ORDERS, which is part of the Local View, is actually deleted. What I mean is that if I mark a record for deletion, which affects the ORDERS table through the LV_ORDERS Local View, and I then save that deletion, and close the form, the next time I open that form, and go to the record previously marked for deletion, that record does not appear to be deleted anymore. Is it that Views cannot see that a record is marked for deletion?
>
>I have a utility which allows the user to permanently delete the records which have been marked for deletion. That utility is accessible through the ADMIN menu item after the user leaves the ORDERS form. But, Id' still like the user to still see any records which have been marked for deletion, regardless of whether or not the user leaves the form and comes back to the form and record later.
>
>Obviously, I've written more on this than it is worth, but this is my concern. Has anyone run up against this situation?