Bill: I can't imagine that "on close designer" action would have any impact, would you? I always do a "create temp table" in the "on before design" (never do a drop in case I have a temp table already there with good data in it), and I have never used the "on close designer". Felt there was no harm in keeping the temp table out there. Since temp tables are session specific I'm not sure how you could have an application running and maybe using this table the same time you would have a form designer up...
Some people mentioned that they drop and create temp tables in the form "on before start" and "on after close" eeps (something else I've never done), and I certainly can see THAT as a problem. Dropping a table that the form is based on while the form is still in memory... doesn't seem like a good idea. > Thanks, Razzak, and John and Paul and Rachael and Sami and Dennis and > others. You've all had great suggestions, and I think Razzak nailed the main > problem with some forms that were creating and dropping their own temp > tables, even in their own "on close designer" actions. > > Bill >
