/build/static/layout/Breadcrumb_cap_w.png

App-V Word 2003 Mailmerge Problem

I am currently trying to App-V a small suite of applications (no DSC linking). One of them automatically opens Word 2003 and then performs a mailmerge to create a document. The base build is 32 Bit Windows 7 with Office 2007.

The suite of applications work ok together on the sequencing PC, I thought Word 2003 would be a pain being installed next to Office 2007 but it actually installs and works ok, I did put a small reg fix in to stop it self healing each time it is launched but apart from that it's ok.

The problem I have is that when I run the application via App-V on another workstation, instead of importing the data (it prompts with a Select * From blah as per normal) it just shows the field codes and not the data, if you then show the mailmerge toolbar and click Toggle data it then shows the data ok. By default the data should appear straight away with no toggling.

To try and resolve this I went through a lot of the Office 2003 keys and eventually found something that may be causing an issue, under HKLM\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components there was a guid that pointed to C:\PRogram Files\Common Files\Microsoft Shared\VBA\VBA6\VBE6.dll , if I take this reg key out and start the application and perform a mailmerge, Office 2003 fires up but then moans about the VBA Feature missing and do I want to install it. If I click No I then I get various macro warnings/errors & VBA not installed but Word then eventually fires up and the data has imported automatically as it should.

So I have two ways of trying to resolve this, the first is trying to understand why the virtualized key pointing to VBE6.dll seems to stop the automatic mailmerge happening. The second is to remove that key and try and stop the Feature Install prompt and macro/VBA warnings that appear. I've tried both approaches but have hit a brick wall with this now.

The VBE6.dll file exists on the workstation and I've tried pointing it elsewhere under the virtualized key, I've also tried merging the key etc.

Any help gratefully received.


0 Comments   [ + ] Show comments

Answers (1)

Posted by: vineetmachhe 10 years ago
White Belt
0

Plz provide the registry u mentioned to suppress selfheal of word 2003

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ