Thunderstone Support Forums

In my code there is a DROP TABLE statement inside of a loop. When it runs, the tables are dropped (i.e., afterward they are no longer in the SYSTABLES table) but the underlying .tbl files are not deleted. When I issue the same DROP TABLE statements from the TSQL prompt, the files *are* deleted.

I thought that perhaps it's a permissions issue, but the user under which the code runs has "Full Control" permissions in the directory where the .tbl files reside.

Any ideas what I might be missing?

Thanks

If this is Windows, then another file handle to the .tbl is probably still open, either from another Texis process, or the same one that DROPped it (e.g. a cached handle from the same or previous statement).

might a sqlcp cache close help?

Thanks, Kai! A judicious call to <sqlcp cache close> prior to the DROPs did the trick!