S
Sineesh
Our application is an excel application and has been developed in VBA.
On few machines, we are facing the problem in executing this application on
two scenarios.
1) When we do fresh installation and tried to load the application would end
up with following error
"Excel.exe has generated errors and will be closed by Windows. You will
need to restart the program. An error log is being created".
After Repairing Microsoft Office 2000 Developer SR-1- ActiveX, the problem
is solved.
2) In our application, we have an option called "Load Topology", which loads
.top file. When we tried to load the top file, the application end up with
an error mentioned above. Again, we repaired Microsoft Office 2000 Developer
SR - 1 - ActiveX to solve this problem.
Also, above-mentioned error occurs when we tried to modify and save our
application. Hence, we tried to identify the root cause of this problem. As
it's not able to simulate this error on our machines, we are clueless about
this issue. But, we suspect that there may be some DLL conflict would have
been occurred on the machines where we need to repair Microsoft Office 2000
developer SR - 1 - Activex.
Could anybody help us out in identifying the root cause of this problem
On few machines, we are facing the problem in executing this application on
two scenarios.
1) When we do fresh installation and tried to load the application would end
up with following error
"Excel.exe has generated errors and will be closed by Windows. You will
need to restart the program. An error log is being created".
After Repairing Microsoft Office 2000 Developer SR-1- ActiveX, the problem
is solved.
2) In our application, we have an option called "Load Topology", which loads
.top file. When we tried to load the top file, the application end up with
an error mentioned above. Again, we repaired Microsoft Office 2000 Developer
SR - 1 - ActiveX to solve this problem.
Also, above-mentioned error occurs when we tried to modify and save our
application. Hence, we tried to identify the root cause of this problem. As
it's not able to simulate this error on our machines, we are clueless about
this issue. But, we suspect that there may be some DLL conflict would have
been occurred on the machines where we need to repair Microsoft Office 2000
developer SR - 1 - Activex.
Could anybody help us out in identifying the root cause of this problem