>>> Running Access 10
>>>
[quoted text clipped - 28 lines]
> programmatically each time? How is that different from populating end
> deleting the data in the table?
From a bloat standpoint they're both not good, but creating and deleting
even an empty table will cause some bloat so it is the worse of the two. To
avoid bloat altogether you would use a table in a temp database, but that
doesn't address your original problem. If you tried to delete the temp
database in the close event of your report the same error would occur
(attmepting to delete an object that is still in use). However; regardless
of whether it is in the same file or a temp file emptying the contents of
the table instead of trying to delete it entirely can be done in the report
close event without a problem.

Signature
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com
Larry Hodges - 19 Jul 2005 22:13 GMT
>>>> Running Access 10
>>>>
[quoted text clipped - 39 lines]
> of trying to delete it entirely can be done in the report close event
> without a problem.
Yes, it does work....thanks.

Signature
-Larry