VB6 Components and References
Please tell me what are these Components and References in a VB6 apps:
COMPONENTS:
- Microsoft ADO Data Control 6.0 (SP6) (OLEDB)
- Microsoft DataGrid Control (SP6) (OLEDB)
- Microsoft Windows Common Controls-2 6.0 (SP6)
REFERENCES::
- Visual Basic For Applications
- Visual Basic runtime objects and procedures
- Visual Basic objects and procedures
- OLE Automation
- Microsoft Active X Data Objects 2.5 Library
- Microsoft Data Binding Collection VB 6.0 (SP4)
COMPONENTS:
- Microsoft ADO Data Control 6.0 (SP6) (OLEDB)
- Microsoft DataGrid Control (SP6) (OLEDB)
- Microsoft Windows Common Controls-2 6.0 (SP6)
REFERENCES::
- Visual Basic For Applications
- Visual Basic runtime objects and procedures
- Visual Basic objects and procedures
- OLE Automation
- Microsoft Active X Data Objects 2.5 Library
- Microsoft Data Binding Collection VB 6.0 (SP4)
ASKER CERTIFIED SOLUTION
![Avatar of Guy Hengel [angelIII / a3]](https://filedb.experts-exchange.com/files/public/2013/11/25/ddbe0ea6-aa6e-4279-b781-57b735dd3ea0.jpeg){kind=small}
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
the only things I include is this (to work with databases):
COMPONENTS:
- Microsoft Windows Common Controls-2 6.0 (SP6)
REFERENCES::
- Visual Basic For Applications
- Visual Basic runtime objects and procedures
- Visual Basic objects and procedures
- OLE Automation
- Microsoft Active X Data Objects 2.5 Library
data controls are not needed.
the data grid control is either too basic (limiting) or to cumbersome (taking control away) for a real data application.
a well-developed form with unbound controls works just well, using stored procedures on the database side to handle the data access in short.
COMPONENTS:
- Microsoft Windows Common Controls-2 6.0 (SP6)
REFERENCES::
- Visual Basic For Applications
- Visual Basic runtime objects and procedures
- Visual Basic objects and procedures
- OLE Automation
- Microsoft Active X Data Objects 2.5 Library
data controls are not needed.
the data grid control is either too basic (limiting) or to cumbersome (taking control away) for a real data application.
a well-developed form with unbound controls works just well, using stored procedures on the database side to handle the data access in short.
ASKER
Fully understood, thanx.
What about the "OLE Automation", what's used for? Why would I want it in my VB app?
What about the "OLE Automation", what's used for? Why would I want it in my VB app?
only if you need to automate other applications (for example ms office ...) via ole automation.
ASKER
ok thanx
ASKER
So if I were to work with databases (SQL, Access, etc.) I have to have both "Microsoft ADO Data Control 6.0 (SP6) (OLEDB)" and "ADO library, to connect to databases and run queries."?
Whats "OLE Automation" used for?
I know you say you are nite sure, but "Microsoft Data Binding Collection VB 6.0 (SP4)" should also be included if I were to work with databases?