Hi Susan,

Firstly, let's not intertwine too many threads here.

Deleting a customer, regardless of where that action is performed, should not result in some other customer being deleted, or shipto addresses for another customer being deleted. This will only happen if the index is damaged - and this condition is the first thing checked when doing an integrity check. If you ever see such behaviour, and the integrity check is clean, then please bring it to our attention immediately. (Of course, it has to be repeatable, and that can be a challenge.) So, the answer to your first question is "No" - there is no requirement to only delete customers from the server. (and as mentioned before - we don't think it's a good idea to be running any applications (Word, Excel, Explorer, Adagio - anything) on the "server" - especially given how inexpensive hardware is these days.

The integrity does not check order and/or invoices in OrderEntry that have been moved to history so "corrupt" is perhaps too strong a word. Steve's suggestion of using the item and customer number changers to "merge together" items you no longer want to see is the best approach.

FWIW - it's not clear what behaviour people would like to see when they are trying to delete customers and inventory items. I think that the item number changers provide the functionality that most people would like.

You should always be able to delete customers and inventory items without a file problem. The question is what to do about the complaints that the integrity check generates when it discovers an order that refers to that deleted item.

Fong: Nobody should be running any applications on your server (see earlier paragraph). It's a false economy.