Windows 7 Update BrowserFlags and EditFlags in window7 registry via VB code

[nivarshn]

Our application is in VB6 and environment is Window XP. We are using WebBrowser control to display data of Word doc files

i.e. we are opening word files always inside the WebBrowser control.Our application send email to user with body as word

files i.e we paste word file data into email body part.Our VB code is perfectly working with office 2003 and office 2010.

We are doing following changes in window registry via VB code for temporary basis:

1)..HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Word.Document.8\


updating BrowserFlags value to H80000024

2)..HKEY_CLASSES_ROOT\Word.Document.8\


updating EditFlags value to 65536


3)..HKEY_CLASSES_ROOT\Word.Template.8\


updating EditFlags value to 65536


4)..HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Word.Document.12\


updating BrowserFlags value to H80000024

5)..HKEY_CLASSES_ROOT\Word.Document.12\


updating EditFlags value to 65536

6)..HKEY_CLASSES_ROOT\Word.Template.12\


updating EditFlags value to 65536

Now we are migrating environment from WinXP to Win7. I have following query for Win7 environment :

1) Will we able to do registry changes using VB code on the all same path as mentioned above ?

2)Will Word doc files always open inside webBrowser control ?

3)Do we require additional registry changes for BrowserFlags and EditFlags via VB code ?

4)Please suggest us what else we have to do for registry changes and to send email ?


Hi, Is there any updates ?

I am adding one more query . If Win7 support team does not give us rights to change registry then without changing values of BrowserFlags and EditFlags , how word docs files will open in webBrowser control of VB ?

 

[ChatGPT]

It seems like you have a well-defined process for handling Word documents in a WebBrowser control in your VB6 application, and you're now looking to migrate this application from Windows XP to Windows 7. Let's address your queries one by one:

Query Responses:​

1. Registry Changes in Windows 7:
   • Yes, you should be able to make registry changes using VB code on the paths mentioned in your post on Windows 7. However, it's essential to ensure that the user running the VB code has the necessary permissions to modify the registry keys.
   []Opening Word Doc Files in WebBrowser Control:
   • In Windows 7, the behavior of how Word doc files open inside a WebBrowser control should remain consistent with your current setup. If you encounter any issues with this functionality, it might require further debugging based on specific circumstances.
   []Additional Registry Changes:
   • If the existing registry changes for BrowserFlags and EditFlags are crucial for the proper functioning of Word doc files in the WebBrowser control, you might need to ensure that these values are set correctly on Windows 7 as well. It's advisable to test your application on Windows 7 after migration to confirm if any additional adjustments are needed.
2. Suggestions for Registry Changes and Sending Emails:
   • Here are some suggestions for handling registry changes and email functionality:
     • Registry Changes: Verify the paths and values for BrowserFlags and EditFlags on Windows 7. Ensure that your VB code has the necessary permissions to modify these registry keys.
     • Sending Emails: If your email functionality is integrated with Word document content, make sure that the email sending process is functioning correctly on Windows 7. Test the email functionality thoroughly post-migration.

       Handling Registry Changes Without Permission:​

       If the Win7 support team restricts registry changes, you may explore alternative methods for displaying Word documents in the WebBrowser control:
       • Temporary Files: Save the Word document content as temporary files that can be displayed in the WebBrowser control.
       • Use Office Applications: Instead of directly embedding Word content, consider using other Office applications (like Outlook) to handle sending Word documents in emails without the need for registry changes.
       Considering the migration to Windows 7, it's essential to conduct thorough testing and ensure compatibility with the new environment. If you encounter challenges, troubleshooting specific to Windows 7 compatibility might be necessary.