Hi,
First time poster and appreciate any help I can get.
I am using a Access adp and vba to import and export from sql to excel and visa versa.
Depending on the month some of the exports will take up to 20 minutes to finish. I instantiate the excel objects from access and leave them invisible in the background while they are populated.
The problem I have is when a user opens a different excel spreadhseet to work on, this new excel doc loads into the same object as the excel I am using for the export and causes all kinds of failures.
When I first create the excel object and open the template for export, can I somehow lock this object so that nothing interferes with it on any level except for obviously the access project that is controlling it.
I noticed when I run excel.exe it does not load into the same object space, it is only when opening actual saved excel objects that I get these clashes.
Thanks
First time poster and appreciate any help I can get.
I am using a Access adp and vba to import and export from sql to excel and visa versa.
Depending on the month some of the exports will take up to 20 minutes to finish. I instantiate the excel objects from access and leave them invisible in the background while they are populated.
The problem I have is when a user opens a different excel spreadhseet to work on, this new excel doc loads into the same object as the excel I am using for the export and causes all kinds of failures.
When I first create the excel object and open the template for export, can I somehow lock this object so that nothing interferes with it on any level except for obviously the access project that is controlling it.
I noticed when I run excel.exe it does not load into the same object space, it is only when opening actual saved excel objects that I get these clashes.
Thanks