Installing Office 97 breaks UAC setting UI in windows 7
Immediately after installing Office 97, I am no longer able to change the UAC level setting in the "User account control settings" dialog.
I can move the slider bar to a different level up or down but there is no response whatsoever when the ok button is clicked. After un-installing Office 97 completely (I also used eraser97.exe after the normal uninstall process to ensure that it was competely removed), the "User account control settings" dialog no longer even appears when clicking on the "Change user account control settings" link from the Action center.
From the research that I have done so far it seems that this is a common issue with people needing to use Office 97 and it may have something to do with a conflict between the macro protection system in Office 97 and the UAC implementation within Windows 7.
It is still possible to change the UAC settings by making changes directly within the registry but this is less than ideal and shouldn't have to be necessary. I am always logged on as an Administrator and have tried this on 4 seperate computers with exactly the same result.
Please note that I am not able in this case to upgrade to a later version of office. I am using only Access from Office 97 and this contains a particular feature that is absolutely necessary for me, that later versions of Access don't have.I fully understand that Office 97 is no longer supported by Microsoft, but I think that this is irrelevant in this case, as this is a Windows 7 bug when installing software that works correctly on Windows XP. Windows 7 should continue to work satisfactorily whether Office 97 is installed or not, just like any other legacy application. This is particulary true of core aspects such as the UAC.
Note: Other than this issue Access 97 seems to work without problems on Windows 7.
I would be grateful for some assistance with this issue.
Answers
Hi All,
We have now worked out what the specific cause of this problem is.
Office 97 makes many changes to the Windows registry when it is installed. This is to be expected of course.
Unfortunately it changes some existing values in specific registry keys which are the cause of the issue. The changes were appropriate for older versions of windows but definitely not for Windows 7.
What has worked for us is to back-up specific registry key values, install Office 97 and then restore these values.
In each case it is the default value of the key that needs to be restored.
The keys in question are:
HKEY_CLASSES_ROOT\Interface\{B722BCC5-4E68-101B-A2BC-00AA00404770}
HKEY_CLASSES_ROOT\Interface\{B722BCC5-4E68-101B-A2BC-00AA00404770}\NumMethods
HKEY_CLASSES_ROOT\Interface\{B722BCC5-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32
HKEY_CLASSES_ROOT\Interface\{B722BCC6-4E68-101B-A2BC-00AA00404770}
HKEY_CLASSES_ROOT\Interface\{B722BCC6-4E68-101B-A2BC-00AA00404770}\NumMethods
HKEY_CLASSES_ROOT\Interface\{B722BCC6-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32
HKEY_CLASSES_ROOT\Interface\{B722BCC7-4E68-101B-A2BC-00AA00404770}
HKEY_CLASSES_ROOT\Interface\{B722BCC7-4E68-101B-A2BC-00AA00404770}\NumMethods
HKEY_CLASSES_ROOT\Interface\{B722BCC7-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32
HKEY_CLASSES_ROOT\Interface\{B722BCC8-4E68-101B-A2BC-00AA00404770}
HKEY_CLASSES_ROOT\Interface\{B722BCC8-4E68-101B-A2BC-00AA00404770}\NumMethods
HKEY_CLASSES_ROOT\Interface\{B722BCC8-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32
HKEY_CLASSES_ROOT\Interface\{B722BCC9-4E68-101B-A2BC-00AA00404770}\NumMethods
HKEY_CLASSES_ROOT\Interface\{B722BCC9-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32
HKEY_CLASSES_ROOT\Interface\{B722BCCA-4E68-101B-A2BC-00AA00404770}\NumMethods
HKEY_CLASSES_ROOT\Interface\{B722BCCA-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32
HKEY_CLASSES_ROOT\Interface\{B722BCCB-4E68-101B-A2BC-00AA00404770}
HKEY_CLASSES_ROOT\Interface\{B722BCCB-4E68-101B-A2BC-00AA00404770}\NumMethods
HKEY_CLASSES_ROOT\Interface\{B722BCCB-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32
Restoring the original default values of the last 3 keys shown above will in fact by itself restore the normal operation of the UAC settings user interface, but as the other keys are all closely related they should as a matter of course be restored also.
Regards,
John Van De Giessen
- Marked As Answer byJohn Van De Giessen Sunday, November 22, 2009 1:53 AM
- Hi John,I add your fix here :)
Below are the contents for a .reg file containing the original default values that we had in our particular case. If you copy the text into a file and name it with a .reg extension then double clicking on that file will set these values for you.--------------------------------------------------------------------------------------------------------------------------Windows Registry Editor Version 5.00[HKEY_CLASSES_ROOT][HKEY_CLASSES_ROOT\Interface\{B722BCC5-4E68-101B-A2BC-00AA00404770}]@="IOleDocument"[HKEY_CLASSES_ROOT\Interface\{B722BCC5-4E68-101B-A2BC-00AA00404770}\NumMethods]@="6"[HKEY_CLASSES_ROOT\Interface\{B722BCC5-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32]@="{A4A1A128-768F-41E0-BF75-E4FDDD701CBA}"[HKEY_CLASSES_ROOT\Interface\{B722BCC6-4E68-101B-A2BC-00AA00404770}]@="IOleDocumentView"[HKEY_CLASSES_ROOT\Interface\{B722BCC6-4E68-101B-A2BC-00AA00404770}\NumMethods]@="16"[HKEY_CLASSES_ROOT\Interface\{B722BCC6-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32]@="{A4A1A128-768F-41E0-BF75-E4FDDD701CBA}"[HKEY_CLASSES_ROOT\Interface\{B722BCC7-4E68-101B-A2BC-00AA00404770}]@="IOleDocumentSite"[HKEY_CLASSES_ROOT\Interface\{B722BCC7-4E68-101B-A2BC-00AA00404770}\NumMethods]@="4"[HKEY_CLASSES_ROOT\Interface\{B722BCC7-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32]@="{A4A1A128-768F-41E0-BF75-E4FDDD701CBA}"[HKEY_CLASSES_ROOT\Interface\{B722BCC8-4E68-101B-A2BC-00AA00404770}]@="IEnumOleDocumentViews"[HKEY_CLASSES_ROOT\Interface\{B722BCC8-4E68-101B-A2BC-00AA00404770}\NumMethods]@="7"[HKEY_CLASSES_ROOT\Interface\{B722BCC8-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32]@="{A4A1A128-768F-41E0-BF75-E4FDDD701CBA}"HKEY_CLASSES_ROOT\Interface\{B722BCC9-4E68-101B-A2BC-00AA00404770}\NumMethods]@="6"[HKEY_CLASSES_ROOT\Interface\{B722BCC9-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32]@="{A4A1A128-768F-41E0-BF75-E4FDDD701CBA}"[HKEY_CLASSES_ROOT\Interface\{B722BCCA-4E68-101B-A2BC-00AA00404770}\NumMethods]@="5"[HKEY_CLASSES_ROOT\Interface\{B722BCCA-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32]@="{A4A1A128-768F-41E0-BF75-E4FDDD701CBA}"[HKEY_CLASSES_ROOT\Interface\{B722BCCB-4E68-101B-A2BC-00AA00404770}]@="IOleCommandTarget"[HKEY_CLASSES_ROOT\Interface\{B722BCCB-4E68-101B-A2BC-00AA00404770}\NumMethods]@="5"[HKEY_CLASSES_ROOT\Interface\{B722BCCB-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32]@="{A4A1A128-768F-41E0-BF75-E4FDDD701CBA}"------------------------------------------------------------------------------------------------------------------------------Regards.- Marked As Answer byJohn Van De Giessen Sunday, November 22, 2009 1:53 AM
All Replies
Hi John,
This is a compatibility issue of the application. Please run the application using Windows 95 or Windows NT workstation compatibility mode.Please follow the below mention steps,
1) Right click the exe and select the ‘properties’ option
2) Select the Compatibility tab
3) Select the “Run this program in compatibility mode for” check box
4) Select the Windows XP SP2 from the drop down
5) Click on Apply.Right-click the exe and Run as Administrator.
I hope this will resolve this issue. It would be more grateful if you could upgrade to the latest version of Office.
Thanks,
Anbu MS
- Proposed As Answer byM AnbuModeratorTuesday, November 03, 2009 2:20 PM
- Unproposed As Answer byJohn Van De Giessen Tuesday, November 03, 2009 11:33 PM
- Hi Anbu MS,Thankyou for the response. The problem however is not in the running of Access97; this actually runs just fine without having to set a compatibility mode, nor does it need to be run as administrator. (Trying these steps makes no difference at all)The problem with the windows 7 UAC setting UI exists whether Access97 is running or not. The problem exists simply because Office 97 (or any component of it) has been installed.Just for additional information, if you reboot the system and DON'T run Access97 at all, the problem in the UAC settings UI still exists. I.e. It is not in running Access97 that the problem is caused.This very much appears to be a bug in the Windows 7 OS itself.Many thanks,John Van De Giessen
- Isn't this situation exactly what "Virtual XP for Windows 7" is intended for?
- Hi fanfarenj,Thank you for your thought on this.Windows XP Mode does not overcome this problem in all situations.The issues are here as as follows:
- XP Mode is not available for all editions of windows 7 and I cannot enforce which edition the users of my software will use. As a minimum Windows 7 Professional is required. I would recommend a minimum of the professional edition to our clients for other reasons anyway, but I cannot enforce it.
- XP Mode, even on supported editions of windows 7 has specific hardware requirements so that virtualization is supported - It may be some time before all users will have upgraded to suitable systems, particularly when their current systems are in other respects more than powerful enough to run windows 7.
- XP Mode is designed to allow older applications to run properly. Note that in this case the application, Access97, does run properly natively on Windows 7.
This is clearly a bug in Windows 7 and I expect that anything short of a fix or workaround in the OS itself is not going to be a viable solution for this.Please all keep your thoughts coming though, they are greatly appreciated.Many thanks,John Van De Giessen - Well you make some valid points; but for all of these I can imagine a workaround. Of course that may involve a cost you are not willing to incur.
If this is a critical issue I wouldn't wait for an answer to appear on this thread. I would contact Microsoft Technical Support. John,
I tried reproducing the issue, but UAC was working properly even after the installation of Office 97. I would suggest you to restart the machine everytime you change the UAC settings. If you don’t restart the machine after changing the UAC level, the changes won’t get reflected.
Testing the changes in UAC settings:
1) Slide the UAC bar to the top, restart the machine and try changing the Date and Time settings (It will prompt a warning message)
2) Slide the UAC bar to the bottom, restart the machine and try changing the system settings (It won’t prompt any messages)
Note: Sometimes, the change in UAC levels will not prompt the user to restart the machine.
I hope this will resolve the issue.
Thanks, M Anbu- Proposed As Answer byM AnbuModeratorFriday, November 06, 2009 4:35 PM
- Unproposed As Answer byJohn Van De Giessen Wednesday, November 11, 2009 3:47 AM
- I just tried installing Access 97 on a Windows 7 machine (32 bit), and have administrator rights.
It originally failed to install because it couldn't place the system.mdw file in the Windows\System32 folder. When I ran Access 97, it complained that file was missing. After I manually added that file to that folder (I was prompted for my user name and password), and ran Access 97 again, it fails with an out of memory error. I suspect it needs rights to modify that file and Windows 7 isn't giving it to it.
This error is unrelated to Windows 7 and is explained in http://support.microsoft.com/default.aspx/kb/161255. By installing the Office Developer Edition, it's up and running in Windows 7 (so far).
This was not meant to be a proposed answer but at least a confirmation that it can be done.
FYI, I was able to apply the SR-1 Patch, but not SR-2 as the update chokes when it tries to modify the Tahoma font in the Windows folder. So maybe I'm stuck with SR-1 instead of SR-2 on Windows 7. Any suggestions for how to get around this would be appreciated.- Proposed As Answer byLukeChung Friday, November 06, 2009 6:48 PM
- Unproposed As Answer byJohn Van De Giessen Sunday, November 08, 2009 12:07 AM
- Hi M Anbu,This is the first time that I have heard that someone hasn't encountered the problem with setting the UAC level after installing Office 97.Just to review our situation, Office 97 doesn't interfere in any way with the normal functioning of the UAC, just the ability to save the slider bar position in the setting user interface once the slider bar has been moved. In effect the "OK" button does not respond.If we change the UAC level by editing the registry then the UAC will work quite satisfactorily at that changed level. Even the slider bar in the settings user interface will correctly reflect the change if we set the level using this method. We just can't save the level by changing the slider bar in the settings user interface.Is there anyone else who has installed any part of Office 97 and doesn't have this issue?Many thanks,John Van De Giessen
- Hi LukeChung,The out of memory error occurs when installing from an original base level Office 97 install where the system has more than 1 Gigabyte of ram.Installing from a SR1 level install does not have this problem. Also, the problem is corrected after installing from an original base level install after applying service pack 1.To successfully install SR-2, you first need to extract the files from the service pack exe (it is an archive and can be extracted by something like Winzip) and then edit the file named filelist.txt. Remove all lines from it that refer to Tahoma and Comic sans font files. Run the sr2patch.exe from the extracted files and now it should succeed.Regards,John Van De Giessen
John,
I tried with different machines to reproduce this issue, but I couldn’t. Office 97 doesn’t do anything with the UAC settings. Please check whether the Office 97 has a valid license and make sure Windows 7 operating system has all the updates.
After checking with the above mentioned, try reproducing the issue in different machines.
Please post back if you face some issues.
Thanks, M Anbu- Proposed As Answer byM AnbuModeratorThursday, November 12, 2009 11:02 AM
- Hi M Anbu,Firstly let me thank you for your time and effort in this.Our Office 97 install is properly licensed and we are testing installs on both RC and RTM versions of Windows 7 which are activated and have all the updates applied.I am wondering if the difference between the problem occurring or not is in the edition and/or service pack level of the Office 97 installation. Ours may be different to yours.We have been using an "Office 97 Professional SR-1" edition install.I will try installing from a different edition and test the result; We have an original base level install that I can try. I will advise the result.Could you please advise which edition and service release level install that you are using?Many thanks,John Van De Giessen
John,
Here are the edition and Service release I used for testing the issue,
Operating system
Windows 7
Edition
Enterprise
Type
64-bit Operating System
Application
Office 97
Version
8
Edition
Professional
Language
English - US
Thanks, M AnbuHi M Anbu,
I have the same problem. I use Windows 7 Professional 32bit and Office 97 Small Business Edition (all software is Original and Licenced of course...). I'm unable to change UAC setting with the slider bar in control panel. No effect when click OK button. I can only change it using the system registry. Please help.This is the first time that I have heard that someone hasn't encountered the problem with setting the UAC level after installing Office 97.Just to review our situation, Office 97 doesn't interfere in any way with the normal functioning of the UAC, just the ability to save the slider bar position in the setting user interface once the slider bar has been moved. In effect the "OK" button does not respond.If we change the UAC level by editing the registry then the UAC will work quite satisfactorily at that changed level. Even the slider bar in the settings user interface will correctly reflect the change if we set the level using this method. We just can't save the level by changing the slider bar in the settings user interface.Is there anyone else who has installed any part of Office 97 and doesn't have this issue?Many thanks,John Van De Giessen- M Anbu,I have tried installing from a different edition of Office 97 but still get the same problem in the UAC settings user interface.I notice that you are testing the installation on a 64 bit version of windows 7.Would it be possible for you to try installing Office 97 an a 32 bit install of Windows 7 and see what results you get?Many thanks,John Van De Giessen
John,
As mentioned earlier, i tested the application with different machines. I have tried with Windows 7 32 bit and Windows 7 64 bit Operating systems.
Please check whether some other applications installed is affecting the UAC settings. Check with the firewall of the machine as well.
Here are the edition and Service release I used for testing the issue,Operating system
Windows 7
Edition
Enterprise
Type
32-bit Operating System
Application
Office 97
Version
8
Edition
Professional
Language
English - US
- Hi again Anbu,It's very strange that you have no problems...i have only few programs installed atm on my machine:Adobe Flash player 10Avira Antivir PersonalCrysis single player DEMOEVGA Precision 1.8.1Foxit ReaderGoogle ChromeJava 6 update 17Microsoft Excel 97Microsoft Excel Euro Toolbar AddinMicrosoft Visual C++ 2005 and 2008 (with updates)Microsoft Word 97Microsoft SilverlightNvidia DriversNvidia PhysXOpenOffice 3.1Opera 10.01Quicktime alternative 3.0.1Total CommanderTeamSpeak 2 RC2Windows Live EssentialsJuris Data (software for my profession)That's all. Somes of these softwares were installed after the problem was found. My Windows 7 is updated of course. My Office 97 is "Small Business Edition".Searching on the web i found some peoples with the same issue.Any ideas?Sorry for my english anyway.
- Hi All,There is another thread within social.technet.microsoft.com which is discussing this problem, where a number of people are having the same issue.For your reference the thread is titled: Restore Points delete & UAC won't changehttp://social.technet.microsoft.com/Forums/en-US/w7itproinstall/thread/4175502c-13fc-4da8-84d9-db8c8cc3da9aThis is certainly not an isolated issue. There are also discussions on other forums regarding this same issue, none of which have yet proposed a viable solution.I have seen at least one post from a corporate administrator who also has this issue across all the corporate workstations.The common aspect of all of the threads that I have looked at is that the problem occurs immediately after installing Office 97.M Anbu however, has been able to install Office 97 on a number of machines without seeing this issue occur. One notable aspect here is that in his testing, Office 97 has been installed on 32 bit and 64 bit versions of Windows 7 Enterprise.Is it possible that the Enterprise edition of Windows 7 handles some things differently enough to prevent this glitch from occurring?Regards,John Van De Giessen
Hi All,
We have now worked out what the specific cause of this problem is.
Office 97 makes many changes to the Windows registry when it is installed. This is to be expected of course.
Unfortunately it changes some existing values in specific registry keys which are the cause of the issue. The changes were appropriate for older versions of windows but definitely not for Windows 7.
What has worked for us is to back-up specific registry key values, install Office 97 and then restore these values.
In each case it is the default value of the key that needs to be restored.
The keys in question are:
HKEY_CLASSES_ROOT\Interface\{B722BCC5-4E68-101B-A2BC-00AA00404770}
HKEY_CLASSES_ROOT\Interface\{B722BCC5-4E68-101B-A2BC-00AA00404770}\NumMethods
HKEY_CLASSES_ROOT\Interface\{B722BCC5-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32
HKEY_CLASSES_ROOT\Interface\{B722BCC6-4E68-101B-A2BC-00AA00404770}
HKEY_CLASSES_ROOT\Interface\{B722BCC6-4E68-101B-A2BC-00AA00404770}\NumMethods
HKEY_CLASSES_ROOT\Interface\{B722BCC6-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32
HKEY_CLASSES_ROOT\Interface\{B722BCC7-4E68-101B-A2BC-00AA00404770}
HKEY_CLASSES_ROOT\Interface\{B722BCC7-4E68-101B-A2BC-00AA00404770}\NumMethods
HKEY_CLASSES_ROOT\Interface\{B722BCC7-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32
HKEY_CLASSES_ROOT\Interface\{B722BCC8-4E68-101B-A2BC-00AA00404770}
HKEY_CLASSES_ROOT\Interface\{B722BCC8-4E68-101B-A2BC-00AA00404770}\NumMethods
HKEY_CLASSES_ROOT\Interface\{B722BCC8-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32
HKEY_CLASSES_ROOT\Interface\{B722BCC9-4E68-101B-A2BC-00AA00404770}\NumMethods
HKEY_CLASSES_ROOT\Interface\{B722BCC9-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32
HKEY_CLASSES_ROOT\Interface\{B722BCCA-4E68-101B-A2BC-00AA00404770}\NumMethods
HKEY_CLASSES_ROOT\Interface\{B722BCCA-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32
HKEY_CLASSES_ROOT\Interface\{B722BCCB-4E68-101B-A2BC-00AA00404770}
HKEY_CLASSES_ROOT\Interface\{B722BCCB-4E68-101B-A2BC-00AA00404770}\NumMethods
HKEY_CLASSES_ROOT\Interface\{B722BCCB-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32
Restoring the original default values of the last 3 keys shown above will in fact by itself restore the normal operation of the UAC settings user interface, but as the other keys are all closely related they should as a matter of course be restored also.
Regards,
John Van De Giessen
- Marked As Answer byJohn Van De Giessen Sunday, November 22, 2009 1:53 AM
- Hi John,I add your fix here :)
Below are the contents for a .reg file containing the original default values that we had in our particular case. If you copy the text into a file and name it with a .reg extension then double clicking on that file will set these values for you.--------------------------------------------------------------------------------------------------------------------------Windows Registry Editor Version 5.00[HKEY_CLASSES_ROOT][HKEY_CLASSES_ROOT\Interface\{B722BCC5-4E68-101B-A2BC-00AA00404770}]@="IOleDocument"[HKEY_CLASSES_ROOT\Interface\{B722BCC5-4E68-101B-A2BC-00AA00404770}\NumMethods]@="6"[HKEY_CLASSES_ROOT\Interface\{B722BCC5-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32]@="{A4A1A128-768F-41E0-BF75-E4FDDD701CBA}"[HKEY_CLASSES_ROOT\Interface\{B722BCC6-4E68-101B-A2BC-00AA00404770}]@="IOleDocumentView"[HKEY_CLASSES_ROOT\Interface\{B722BCC6-4E68-101B-A2BC-00AA00404770}\NumMethods]@="16"[HKEY_CLASSES_ROOT\Interface\{B722BCC6-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32]@="{A4A1A128-768F-41E0-BF75-E4FDDD701CBA}"[HKEY_CLASSES_ROOT\Interface\{B722BCC7-4E68-101B-A2BC-00AA00404770}]@="IOleDocumentSite"[HKEY_CLASSES_ROOT\Interface\{B722BCC7-4E68-101B-A2BC-00AA00404770}\NumMethods]@="4"[HKEY_CLASSES_ROOT\Interface\{B722BCC7-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32]@="{A4A1A128-768F-41E0-BF75-E4FDDD701CBA}"[HKEY_CLASSES_ROOT\Interface\{B722BCC8-4E68-101B-A2BC-00AA00404770}]@="IEnumOleDocumentViews"[HKEY_CLASSES_ROOT\Interface\{B722BCC8-4E68-101B-A2BC-00AA00404770}\NumMethods]@="7"[HKEY_CLASSES_ROOT\Interface\{B722BCC8-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32]@="{A4A1A128-768F-41E0-BF75-E4FDDD701CBA}"HKEY_CLASSES_ROOT\Interface\{B722BCC9-4E68-101B-A2BC-00AA00404770}\NumMethods]@="6"[HKEY_CLASSES_ROOT\Interface\{B722BCC9-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32]@="{A4A1A128-768F-41E0-BF75-E4FDDD701CBA}"[HKEY_CLASSES_ROOT\Interface\{B722BCCA-4E68-101B-A2BC-00AA00404770}\NumMethods]@="5"[HKEY_CLASSES_ROOT\Interface\{B722BCCA-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32]@="{A4A1A128-768F-41E0-BF75-E4FDDD701CBA}"[HKEY_CLASSES_ROOT\Interface\{B722BCCB-4E68-101B-A2BC-00AA00404770}]@="IOleCommandTarget"[HKEY_CLASSES_ROOT\Interface\{B722BCCB-4E68-101B-A2BC-00AA00404770}\NumMethods]@="5"[HKEY_CLASSES_ROOT\Interface\{B722BCCB-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32]@="{A4A1A128-768F-41E0-BF75-E4FDDD701CBA}"------------------------------------------------------------------------------------------------------------------------------Regards.- Marked As Answer byJohn Van De Giessen Sunday, November 22, 2009 1:53 AM
