Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
rip.murdock
Starting Member
4 Posts |
 Posted - 2005-11-18 : 10:55:39
|
| The samples in my VB for SQL Server book are in VB 6. I’m just getting started with Visual Studio .NET 2003.The conversion wizard is looking for missing referenced components:MSHFLXGD.OCX (6.0.0)MSADODC.OCX (6.0.0)MSDERUN.DLLMSBIND.DLLMSDE.DLLHow can I get the referenced components? |
|
|
Hommer
Aged Yak Warrior
808 Posts |
Posted - 2005-11-18 : 12:09:12
|
| you have to look them up one at a time. As I know, there is no easy way to get around this.You have to find out who the vendors are, if they are from thrid party. Then find out if they have dot net version of the control.If the dll/ocx are developed in house, you need to convert them first.Some of them may already have their counter parts in the dot net world, but sorting them out and verifying their functionalities meet your app requirements is a huge battle. |
 |
|
|
|
|
|
Visual Basic 6 components