Supporting both access and sql

External Since: Aug 31, 2003 Posts: 136

What makes you think that VB.NET is less stable than C#? They provide
virtually identical functionality, speed and stability.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
<a style='text-decoration: underline;' href="http://www.betav.com" target="_blank">www.betav.com</a>
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________

"Ralph" <msnews.20.nt_consulting32.RemoveThis@spamgourmet.com> wrote in message
news:uevBzE1BFHA.3336@TK2MSFTNGP11.phx.gbl...
>
> "D" <Dave.RemoveThis@nothing.net> wrote in message
> news:umm4dgtBFHA.2428@TK2MSFTNGP14.phx.gbl...
  >> Hey thanks for that detailed explanation. It made perfect sense, I've
> worked
  >> with interfaces and polymorhphism in c++ before but I didn't make the
  >> connecton with how well it would apply to this problem.
  >>
  >> This project is currently in vb6 so am I correct in saying that it will
> have
  >> to be done in vs.net to use interfaces?
  >>
  >> If I open the project in vs.net I assume it'll ask to convert the project
  >> over to .net. I wonder if it'll compile ok. I'm thinking if it compiles
  >> ok
> I
  >> can start building the business class and take each database one by one
> and
  >> start converting the code to use the business class.
  >>
  >> Thanks again, I have alot to think about now.
  >>
>
> No. What I showed applies to VB6.
>
> Interfaces are in a sense an 'abstract' class, and what I outlined,
> demostrates the same syntax as a class yet declared as an interface. VB6
> doesn't support implementation inheritance only interface inheritance.
> [ps
> I screwed up when I declared them as "Interface Ixxx" in my sample 'sub
> main' code - I meant to say "Implements Ixxxx" - sorry about that.]
>
> VB.net is a totally different ball game. It does support both Interfaces
> (Abstract Classes) and implementation inheritance - a la C++ (a slight
> subset as it doesn't support multiple inheritance and you can only derive
> from one class.) But it is a full-blown OOPL. You don't have to use VB.net
> to do what I borishly outlined above <g>. And with VB.Net you have even
> other options.
>
> You are correct the basic "OO"-ness is the same in any OOPL.
>
> If .NET is an option for your project and you want to go that way, then
> definitely use .NET. It appears to be the wave of the future. (Although
> frankly I would use C# in .net as the language is likely to be more
> stable.)
> However, it will entail a complete re-write of your application. You will
> find that the conversion wizard only works "kind-of". The result will be a
> hybrid that isn't all that efficient or that straight-forward.
>
> There is only an 'appearance' of a common language between the two
> environments. Everything else is totally different. ADO.NET is very
> different from ADO. They are worlds apart.
>
> hth
> -ralph
>
>
>