Was there a hidden Excel window, only detectable as an extra item listed in
the Task Manager?

If this remains after running your automation code, you need to make sure
that at the end of your routine you close all documents, release all object
variables, then quit Excel and release the Excel application variable.

You ought to be able to find something relevant on Google. I have not used
versions of VS later than 6 to do this, so I don't know the steps.

- Jon
-------
Jon Peltier, Microsoft Excel MVP
Tutorials and Custom Solutions
Peltier Technical Services, Inc. - http://PeltierTech.com
_______


"htrajt" wrote in message
...
I thought Vb6 only because when you go to "about" under the macro screen it
reads that way, but I am like you in thinking it is actually using
Microsoft
Visual Studio 2003 which is installed on my pc. If the process is not
closing, then I will need to write a subroutine that does this? I don't
get
many crashes while the files are being built. Just today I opened
"Program.xls" (after I had rebooted and opened other excel files, (but not
this one), an hour later after closing all the other excel files,
Program.xls
gave me the same read only message.

"Jon Peltier" wrote:

I wonder whether you're confusing VB6 and VBA.

If you are referring to VB6, did your automation properly shut down the
instance of Excel used when creating the workbook? If not, there may be a
hidden instance of Excel, which has a copy of the file open. Look in the
Task Manager for extra EXCEL.EXE processes.

- Jon