I would have to guess that you are using some object(s) that are not fully
qualified and/or released before attempting to close the file
But without any idea of your code, it's hard to tell.

NickHK

"Arif Ali" <Arif wrote in message
...
I have a rudimentary pricing applicatiion which copies information from a
pricelist into a quote form located on a sheet within the same workbook.
The
user has a toolbar that they can use to copy this quote sheet to a new
file.
The program also saves a listing of all quotes generated in this fashion
into
a summary sheet. After creating the quote file, the application closes
the
new quote and allows the user to generate a new quote.

The problem is that after generating several quotes (like 2-3), and
viewing
the summary list of quotes once or twice, Excel starts acting really
strange.
the panes lockup memory errors occur, etc. When running this project in
debug mode, the VBAProjects associated with the closed workbooks are still
in
memory. So after a while there can be 5-10 sets of VBAProjects (with no
code
or userforms at all) in memory.

In the past I learned that using fully qualfiied workbook, sheet and range
names eliminated similar problems. But even with fully qualified
references,
this problem remains. I am urgently trying to release the latest version
of
this tool to my coworkers, but I am stumped as to the cause of this
problem.

Any ideas?

Thanks,