Hi all
We have a bespoke in-house application that performs a mail merge into Microsoft Word. Under Office 2000 - we had no issues. However, recently we upgraded from Office 2000 to 2003. Now everytime the application performs the mail merge, Word starts up showing the Windows Install dialog box. It takes a couple minutes to run through - but does not ask for the disk (We did not delete the install files from the machine). The problem is that it doesn't just occur the first run we run it (as one might expect). It runs everytime the application starts Word to open the merge document. Some of the things we have tried to troubleshoot the problem included:
+> Performed a "Full - Run from the PC" install of office.
+> Given the user Local Administrative rights on the system.
+> Perform the initial office Full install as the user - i.e. logged on under their profile.
+> Left the install files on the system after the install was completed.
+> Run Word, and from the help menu selected a detect repair.
The interesting thing is that after every Install process, the Application log shows an MSInstaller message saying office installation was completed successfuly. The problem does not prevent the merge from running, it just delays the process by 40 seconds whilst the Windows installer run. That said, it is starting to annoy the end users on site. On a side note, running a mail merge from within Word does not generate this problem. I have tested with Excel spreadsheet data source.
Does any one have any ideas / debugging tricks they could suggest? (installing OpenOffice is not a viable solution
Cheers
Rob
We have a bespoke in-house application that performs a mail merge into Microsoft Word. Under Office 2000 - we had no issues. However, recently we upgraded from Office 2000 to 2003. Now everytime the application performs the mail merge, Word starts up showing the Windows Install dialog box. It takes a couple minutes to run through - but does not ask for the disk (We did not delete the install files from the machine). The problem is that it doesn't just occur the first run we run it (as one might expect). It runs everytime the application starts Word to open the merge document. Some of the things we have tried to troubleshoot the problem included:
+> Performed a "Full - Run from the PC" install of office.
+> Given the user Local Administrative rights on the system.
+> Perform the initial office Full install as the user - i.e. logged on under their profile.
+> Left the install files on the system after the install was completed.
+> Run Word, and from the help menu selected a detect repair.
The interesting thing is that after every Install process, the Application log shows an MSInstaller message saying office installation was completed successfuly. The problem does not prevent the merge from running, it just delays the process by 40 seconds whilst the Windows installer run. That said, it is starting to annoy the end users on site. On a side note, running a mail merge from within Word does not generate this problem. I have tested with Excel spreadsheet data source.
Does any one have any ideas / debugging tricks they could suggest? (installing OpenOffice is not a viable solution
Cheers
Rob
