>>Hi All, >> >>I cannot find anywhere a discussion on the relative merits of : >> >>- Using the Data Environment to open all required files >>- Coding the Opening of files >>- Using Table Views. >> >>Any ideas, or any article one can refer me to ? >> > > >I generally like to use private datasessions, so using the DE is the logical choice. I like the flexibility of multiple sessions of a form without going crazy trying to handle open tables through code. I do, however, use code to open tables or views for quick lookups or validation and them close them again...really depends on frequency of usage. > >I use updateable, parameterized views for virtually ALL parent-child or table subset situations. I think I've forgotten the syntax of SET RELATION ;-)

I love parameterized views, as long as the DBC doesn't break. I've found that the DBC is more sensitive to corruption when an app abends than the dbf's are. And the view is stored only in the DBC. I hate to restore an entire set of tables and have the clerks re-enter data and redo procedures. It would be easy if one could merely overwrite the corrupt DBC files with a good backup set, but it doesn't always work that way because it appears that the table headers and the DBC have a unqiue stamp that connects them, and even though you try to connect a table back to a DBC it won't let you unless you open the table in the "other" mode and answer yes to the unlink question. Then you can add the table back to the restored DBC. No problem for a handful of tables, but when you DBC controls two or three dozen tables - problem.


Note about your signature msg: After 34 years as a Republican I've switched to the Libertarian party! Let's keep the ALL of the amendments and tell the PC police to find honest work!