T
Troy
Hi...
Not sure if this question belongs in an Excel group, or here. Since the code
is all executed from Access, I'll try here first.
In a nutshell, Access 2000 module exports form data in xls format using
OutputTo, then creates Excel object, opens created xls file, formats data
and graphs it.
Last code line executed sets excel object equal to nothing. The form is left
open to be saved as some file name by user.
My problem is, after the excel workbook is closed by the user, it remains in
the task manager list of running processes until the Access database itself
is closed. This causes a problem if the module is run again with different
parameters.
Anyone run into this? Am I mistaken in thinking that setting the excel
object to nothing is freeing it from the access code that created it?
Any help would be appreciated!
Not sure if this question belongs in an Excel group, or here. Since the code
is all executed from Access, I'll try here first.
In a nutshell, Access 2000 module exports form data in xls format using
OutputTo, then creates Excel object, opens created xls file, formats data
and graphs it.
Last code line executed sets excel object equal to nothing. The form is left
open to be saved as some file name by user.
My problem is, after the excel workbook is closed by the user, it remains in
the task manager list of running processes until the Access database itself
is closed. This causes a problem if the module is run again with different
parameters.
Anyone run into this? Am I mistaken in thinking that setting the excel
object to nothing is freeing it from the access code that created it?
Any help would be appreciated!