Hi Christof,

>Hi Colin,
>
>>Todays apps still contain a LOT of pure xBASE code, it just the programming structure, OOP vs Procedural, that's changed.
>
>But today applications are more often using SELECTs, views, working on buffers, etc. Not everyone is writing such application, of course, but I think we are moving in that direction.

The only thing here that is probably affected by DELETED() tag would be views. I've used SELECT's for things like reports, popups, etc for years to avoid speed killers like SET FILTER.
>
>>I have never recycled records, and that's dating back to the FoxPro 1 days
>
>You didn't, but a lot of people did, to avoid packing, or because disk space was not available.

And a lot of people didn't so I don't believe this one really applies.
>
>>SQL and RECCOUNT() have been available for years and I've used them for years.
>
>RECCOUNT() has been available, but you can't use it on a table that contains deleted records to find out whether there's a record in it or not.

That is as true now as always. I don't see the point.
>
>>I've run a number of apps since 2.5 over dial-up lines
>
>I don't think this was as widely used as it is now... More often in that time, we have run FoxPro via a tool like PCAnywhere that only transfers the GUI and keystrokes, but not accessed data directly on a remote server.

Actually, at the time, the company was using a product called CoSession and are now using Citrix. Now, only GUI, keystrokes and mouse clicks are transferred but then all the processing was performed by the clients CPU.

Personally, IMHO, based on posts from you and others, I am under the belief now that a DELETED() tag has *always* been a bad idea for most situations.
>
>
>Christof

Cheers,