>>I was just thinking to program something very similar to your FAQ #31943 (close all files opened after a certain point), and then decided to look in downloads and FAQ first. The FAQ served its stated purpose very well, after a few minor adaptations (I preferred to have a visual class, and I had to get rid of the last two parameters in aseek(), since we still use VFP 6).
>
>My only problem with this class is why didn't I think of it earlier. I wish I wrote this in at least 1999 :).

My ideas on programming such a class went along the same lines: the object should check what aliases were open, and close when it is destruyed.

For now, I have used your class in the reporting engine, which regularly opened lots of tables, and kept them open until the user closed the form with the report options. I figured that closing as soon as the report was produced should produce less maintenance trouble, since sometimes we have to politely ask users to leave the system - or if that fails, trigger an auto-close for all users.