- MICROSOFT DATA BINDING COLLECTION VB 6.0 SP4 REGISTRATION
- MICROSOFT DATA BINDING COLLECTION VB 6.0 SP4 ZIP
The applications works on my machine and the application is distributed to many customers where it does work just fine. Posted by ddolph (Owner) on 07:42:00 PM I’m not sure I understand. _ From: ddolph via visualstudio-l Sent: Monday, Novem4:41 PM To: css nico Subject: RE: VB 6 program dissappears At least once you know what the problem is, you can start working towards solving it.
![microsoft data binding collection vb 6.0 sp4 microsoft data binding collection vb 6.0 sp4](https://flylib.com/books/3/405/1/html/2/images/fig364_01.jpg)
That’ll be cheaper and quicker to accomplish. Then you can conclusively determine whether your dll’s end up in the system folder. You could write a small app that does not rely on dll’s that will produce and email to you the properties of the dll’s that are resident on their computers. Which means it will look at an updated dll without recognizing that your dll is different and not copy yours forward. I would bet a dollar to a doughnut that the deployment package checks to see if there is already a shared dll in the system and then not write yours away.
![microsoft data binding collection vb 6.0 sp4 microsoft data binding collection vb 6.0 sp4](https://docplayer.net/docs-images/43/10289699/images/page_8.jpg)
Here’s a snapshot of the Setup.lst Bootstrap section. The Package & Deployment Wizard didn’t move these bootstrap DLL’s. I installed the program and it still works fine on my machine but fails to load on my customer’s machine. Itircl.dllĚppPath itss.dllĚppPath mesa.dllĚppPath mfc42.dllĚppPath MSRDO20.DLLĚppPath MSSTDFMT.DLLĚppPath MSVCRT.DLLĚppPath RDOCURS.DLLĚppPath VB5DB.DLLĚppPath
MICROSOFT DATA BINDING COLLECTION VB 6.0 SP4 REGISTRATION
Would my customers have to go through some registration process on their machine to get the application to run? I don’t understand this DLL Registration thing.
![microsoft data binding collection vb 6.0 sp4 microsoft data binding collection vb 6.0 sp4](https://csharpcorner-mindcrackerinc.netdna-ssl.com/UploadFile/e95fe7/introducing-data-binding-with-windows-form/Images/DatBinding1.jpg)
I’m assuming that I will be able to change the Package and Deployment Wizard to put the DLL’s into a separate folder, but the next line threw me. Since my application runs on most machines and only fails on a handful of others, your description of the problem seems right on. Posted by ddolph (Owner) on 10:44:00 AM Thanks Nico. _ From: ddolph via visualstudio-l Sent: Sunday, Novem6:12 AM To: css nico Subject: RE: VB 6 program dissappears That way you don’t need to formally uninstall it either you just delete your folder and your application is gone. Change your package wizard to deploy your dll’s in the same folder as your application. Some dll’s require specific registration my experience is that VB6 does the registration for you, so don’t pay too much attention to that one. I don’t understand what’s happening here. I can’t debug the problem because I don’t have access to the customers machines. The program terminates itself immediately. The installation process works fine and the program runs on my machine and most of my customers, but, on some machines when you start the program the splash screen appears but the main program never appears.
MICROSOFT DATA BINDING COLLECTION VB 6.0 SP4 ZIP
I zip the resulting files and distribute the program. I compile my application and then use the Package and Deployment wizard. Posted by ddolph (Owner) on 08:37:00 PM I’m running XP SP2, Visual Studio VB6. _ From: ddolph via visualstudio-l Sent: Saturday, Novem3:03 PM To: css nico Subject: VB 6 program dissappears Your application won’t enjoy DLL upgrades either, but that’s the best news ever since you want to control your DLL upgrades with your own version changes and not with that of other applications. In that manner unrelated upgrades cannot break your application. If they require registration, register them from your own, unique location. My advice is to deploy ALL your DLL’s in your own application folder and not in the system folder. Even DLL’s with the same name and function can with an upgrade, totally unrelated to your application, lose some of their functionalities and have them bundled in with other DLL’s, without reasonable warning. If a customer has upgraded anything that involves those DLL’s, your application can break and behave typically like you describe. dll’s in the same folder and in the same hive in the registry so that they can be shared.
![microsoft data binding collection vb 6.0 sp4 microsoft data binding collection vb 6.0 sp4](https://bettersolutions.com/vba/controls/datetimepicker-additionalcontrols.png)
In some cruel, demonic wisdom Microsoft bundles all. You most probably are up against what is known as DLL-hell.