>BTW, If you keep all files open from the start of your applications and never close them during the run, I'm am really impressed that you have never experienced corruption due to this practice. I suspect you have been very lucky or have perfect, stable power and networks. Neither of which is the norm in most places that I have seen.
>
Been practicing a long time!:o). Cut my baby teeth on 16bit cpm xbase. Made me mean - a code yard dog! An evolved (seasoned:), flight tested frame work is always helpful [too]! I am fortunate to be able to work projects with some real good (mom `n pop) nw engineers. The projects require a min hardware spec. Nobody wins at down-time!

I worked at a Computerland early in my carrer. A government purchase specified systems and maximum configuration, awa applications software. The version of lotus (1A?) would not work with the with the specified memory. The government did not want to change the requisition to specify more memory. So, we ordered earlier versions (1.0). I think the users were limited to 40 line spread sheets. It was a no value deal. Lesson: Tell the buyer it won't work and [that] they will need to make their purchases someplace else.

Software should be easy to use and never break. This is achievalble. But all the components of the configuration (including the app) have to be of the highest quality. As Granny says "You don't want to end up penny rich and dollar poor!:-)