Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.
Solved
Installing a VB6 OCX
Posted on 2012-12-21
My application uses the VB6 FlexGrid. When assembling an installment package I include MSFLXGRD.OCX. I need some education.
Question: Is it necessary for the installer to register this OCX on the target machine?
Question: Does it matter where the installer puts this file? Is the installation folder for the application all right?
Question: This application was developed under XP. Will there be a problem installing to Win7 (or 8 or etc…)?
Question: Is it necessary for the installer to register this OCX on the target machine?
Question: Does it matter where the installer puts this file? Is the installation folder for the application all right?
Question: This application was developed under XP. Will there be a problem installing to Win7 (or 8 or etc…)?
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
3 Comments
Active today
>>Question: Is it necessary for the installer to register this OCX on the target machine?
Yes. All ActiveX components need to be registered.
>>Question: Does it matter where the installer puts this file? Is the installation folder for the application all right?
No. the Default Windows\System32 is the right place. A single component (MSFLGXGRD for instance) can only be installed once on a computer. The registry will indicate where it is located.
>>Question: This application was developed under XP. Will there be a problem installing to Win7 (or 8 or etc…)?
It should.
Yes. All ActiveX components need to be registered.
>>Question: Does it matter where the installer puts this file? Is the installation folder for the application all right?
No. the Default Windows\System32 is the right place. A single component (MSFLGXGRD for instance) can only be installed once on a computer. The registry will indicate where it is located.
>>Question: This application was developed under XP. Will there be a problem installing to Win7 (or 8 or etc…)?
It should.
If you are using the VB Package & Deployment Wizard to create a "setup.exe", and your "Package type" is "Standard Setup Package":
1. "setup.exe" will register the OCX for you, additional steps by the installer to manually register the OCX is not necessary.
2. OCX and DLL files that will be common across all applications should be installed into the "$(WinSysPath)" as set in the Wizard on the 'Install Locations" screen.
If you create your own OCX or DLL (such as an ActiveX exe), those should be installed in the "$(AppPath)". However, these too can be installed in "$(WinSysPath)" if you can insure that your OCX/DLL will have a unique name, and that name changes any time you break binary compatability.
3. Common Window's OCXs shouldn't have problems at this time if you're XP system was brought up to date with the latest fixes the Microsoft ever released. But then again, you're at the mercy of what Windows will or will not manage to "break" going forward as VB6 is no longer supported. You're more likely to run into issues if you have 3rd party dependancies.
If you do have issues, you might be able to solve them (at least on Windows 7) by using the Virtual XP machine. We so far have not had any issues continuing to maintain and support our VB application on the Virtual XP machine running on Windows 7.
1. "setup.exe" will register the OCX for you, additional steps by the installer to manually register the OCX is not necessary.
2. OCX and DLL files that will be common across all applications should be installed into the "$(WinSysPath)" as set in the Wizard on the 'Install Locations" screen.
If you create your own OCX or DLL (such as an ActiveX exe), those should be installed in the "$(AppPath)". However, these too can be installed in "$(WinSysPath)" if you can insure that your OCX/DLL will have a unique name, and that name changes any time you break binary compatability.
3. Common Window's OCXs shouldn't have problems at this time if you're XP system was brought up to date with the latest fixes the Microsoft ever released. But then again, you're at the mercy of what Windows will or will not manage to "break" going forward as VB6 is no longer supported. You're more likely to run into issues if you have 3rd party dependancies.
If you do have issues, you might be able to solve them (at least on Windows 7) by using the Virtual XP machine. We so far have not had any issues continuing to maintain and support our VB application on the Virtual XP machine running on Windows 7.
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
If you have ever used Microsoft Word then you know that it has a good spell checker and it may have occurred to you that the ability to check spelling might be a nice piece of functionality to add to certain applications of yours. Well the code that…
This article describes how to use a set of graphical playing cards to create a Draw Poker game in Excel or VB6.
Get people started with the utilization of class modules. Class modules can be a powerful tool in Microsoft Access. They allow you to create self-contained objects that encapsulate functionality. They can easily hide the complexity of a process from…
This lesson covers basic error handling code in Microsoft Excel using VBA. This is the first lesson in a 3-part series that uses code to loop through an Excel spreadsheet in VBA and then fix errors, taking advantage of error handling code.
This l…
- Microsoft Office
- Office 365
- Microsoft Access
- VBA
- Microsoft Excel
- Visual Basic Classic
Suggested Courses
Course of the Month10 days, 14 hours left to enroll
618 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.