Hi there,
I have a problem that I hope somebody can help with.
I have a button on my form which creates an instance of Excel and exports a ListView to an Excel Workbook - This all works perfectly.
Occasionally when I exit my application I get the following error 'The instruction at "0x0adbc609c" referenced memory at "0x00000014". The memory could not be "read".' (This may happen whether the Excel instance my application opened is open or has been closed).
I think that this error may be memory related. Is it possible that my code to export to excel is still 'hanging onto' the exported data?
My questions are:
Any help anyone can offer is much appreciated...
I have a problem that I hope somebody can help with.
I have a button on my form which creates an instance of Excel and exports a ListView to an Excel Workbook - This all works perfectly.
Occasionally when I exit my application I get the following error 'The instruction at "0x0adbc609c" referenced memory at "0x00000014". The memory could not be "read".' (This may happen whether the Excel instance my application opened is open or has been closed).
I think that this error may be memory related. Is it possible that my code to export to excel is still 'hanging onto' the exported data?
My questions are:
Is there a way for me to clear the memory that has been used during the export to excel - do I even need to do this?
Is there a link that remains between my application and Excel after the workbook has been created? Can I break this link (if one exists) without killing Excel?
When I close my application, can I kill only the Excel instances that were started inside my app and leave externally opened Excel sessions open?
I see a lot of talk about the 'Garbage Collector' mentioned. I also see a lot of people mentioning to be extremely careful when using it. Is this somehting I need to think about using when exporting data to Excel?
Any help anyone can offer is much appreciated...
Last edited: