Hi Darrell

My suggestion is simple: Use SQL and cursors as much as possible. If you take some time and analyse your system, you will probably be able to use SQL so much that your tables will almost never stay open. I have done this myself for many years, and whenever I have a power failure or something, I can be almost sure that my data is safe.

>An application I am working on opens tables at the beginning and does not close the tables until the end. The application does not use private data sessions. The assumption throughout is that these tables are always open. Of course, like many apps, as it expands things accidentally get close, crashes happen, etc. etc. and tables are not always open.
>
>Is it better in methods/programs to make sure the table is first open and if not open it or to generate an error and try to figure out why the table was closed in the first place and fix that problem?