I learned a lot from using Visual Basic. And I won't repeat that mistake.
Visual Basic VB6 Table of Contents TOC
- Visual Basic VB6 Table of Contents TOC
- Program Extension PlugIns DLL SO and Drivers
- Thraex Installer Issues – generates install packages
- VBScript and the VbsEdit Software
- vb6 Using Scintilla SciLexer DLL
- VB6-CoolMenu
- DAO Issues with VB project using database references
- Visual Basic
- Visual Basic VB6 References Used During SKC Software Development
- Visual Basic VB6 Understanding Microsoft Classes
- Visual Basic VB6 Reverse Engineering
End of TOC
DAO Issues with VB project using database references SOLUTION: Microsoft left vb5db.dll off its distribution list!
The solution to all the microsoft database distribution problems! == vb5db.dll is not included in vb6 redist.txt
- DAO problem – Error message 1706
- reference to microsoft office install problem in relation 1706
- Google Search: vb6 dao installation dependency
- How To Ensure Jet 3.5 Is Installed Correctly (Part I)
- How To Ensure Jet 3.5 Is Installed Correctly (Part II)
- Deploy database applications with the Package and Deployment Wizard (PDW)
- How to obtain the latest service pack for the Microsoft Jet 4.0 Database Engine
- Best practices for deploying Visual Basic 6.0 applications – Includes links to several helpful tools for debugging installation problems including dependencies
- PRB: Jet 3.51 OLE DB Provider Is Not Installed With MDAC 2.1 or Later
- How To Control Which MDAC Version the Package and Deployment Wizard (PDW) Distributes When you reference ActiveX Data Objects (ADO) in your Visual Basic 6.0 project, and use the Package and Deployment Wizard to build the install, the wizard uses the MDAC_Typ.exe file in the …\Wizards\PDWizard\Redist directory.
- OLE DB Providers
- Packaging and Deployment Wizard: Description of Setup.lst sections
- How To Have Your ODBC Jet 3.5 and 4.0 Applications Co-exist
- How to obtain the latest service pack for the Microsoft Jet 4.0 Database Engine
- INFO: Deploy database applications with the Package and Deployment Wizard (PDW) appears PDW may automatically use mdac_typ.exe if you add it manually to the file list
- VB6-Datagrid/Adodc Data Binding Error
- Access / JET mdb SQL\
- Win32 SDK Tools > How to Install Is towards the bottom: If you have Microsoft Visual Studio 6.0 and installed the Win32 SDK Tools, you can start Dependency Walker using the following steps:
Click the Start button, point to Programs, point to Microsoft Visual Studio 6.0, and then point to Microsoft Visual Studio 6.0 Tools. Click Depends.
If you do not have the Win32 SDK Tools installed, follow these steps to install them:
- Click the Start button, point to Settings, and then click Control Panel.
- Double-click the Add/Remove Programs icon.
- Click the Install/Uninstall tab, and then double-click Microsoft Visual Studio 6.0.
- In the Setup dialog box, click Add/Remove.
- In the Options list, select Tools (do not click the check box), and then click Change Option.
- Click the Win32 SDK Tools check box to select it, and then click OK.
- Click Continue.
If you have the standalone Visual Basic 6.0 product, you can find Dependency Walker in the COMMON\TOOLS\VB\UNSUPPRT\DEPEND folder on Disk 1.
The Dependency Walker, among other tools, is included with the Platform SDK under the Tools\Platform SDK Tools in the installer. After installing the needed portions of the SDK, you can find Depends.exe on the Start menu underMicrosoft Platform SDK\Tools\Depends. (The utility works on Microsoft Windows 95, Microsoft Windows 98, Microsoft Windows Millennium, Microsoft Windows NT, and Microsoft Windows 2000.) The documentation for the utility is in Depends.hlp, which can be found in \Program Files\Microsoft Platform SDK\Bin.
0 Comments