Thanks for clicking.
Historical we have upgraded our VB6 program to VB.NET using the upgrade wizard.
If VB6 data bindings was classic ADO, the VB.NET converts this to it's own Interop classic ADO control.
Functionally this works fine! However, it won't be supported forever, and we are concerned with how much speed were sacrificing, especially over a network.
We have developed a small application using the BindingSource control, and we can navigate between records easily
My question is this.
Is this control an adequate data control to use on a VB.NET VS2005 application, thinking about it from a speed point fo view, and especially over a network, before we decide to convert over our 150+ forms in our main application??
Also as a cheeky added bonus, if anybody has any idea how much speed we are losing by using classic ADO in a VS2005 environment, it'd be great if you could share with me.
Thanks so much