Re: Vb 6.0 ADO Methodology vs. .NET
From: Val Mazur (group51a_at_hotmail.com)
Date: 07/01/04
- Next message: Gus: ""Invalid character value for cast specification" in Windows XP"
- Previous message: William \(Bill\) Vaughn: "Re: Vb 6.0 ADO Methodology vs. .NET"
- In reply to: Alex Ackley: "Vb 6.0 ADO Methodology vs. .NET"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 1 Jul 2004 15:20:43 -0400
Hi Alex,
ADO is a part of MDAC and MDAC is a part of the operating system. So your
application, which uses ADO, will still work without any changes. One
restriction - on your target PC you should have at least same version of
MDAC or newer one.
.NET framework is completely different approach and it will be used only
with the applications, written in .NET. If you developed your application in
Windows 2003, but using VB6, you do not need to distribute .NET Framework
-- Val Mazur Microsoft MVP "Alex Ackley" <AlexAckley@discussions.microsoft.com> wrote in message news:519A71CB-975B-4308-907E-42B8A59D418D@microsoft.com... > I'm migrating an application that was written in VB 6.0 and runs on a NT > 4.0 platform to a Windows 2003 server. > > I've read that ADO changes from VB 6.0 to .NET and that code needs to be > re-written many times. I'm not a programmer but a server person. So I'm > wondering if anyone knows if an application that makes an enormous use of > ado connections and instances to an Oracle 8 databse can function on a > Windows 2003 server without having to rewrite all code? Or can I not > install a .NET framework and allow it run on a legacy type platform? > > Thanks
- Next message: Gus: ""Invalid character value for cast specification" in Windows XP"
- Previous message: William \(Bill\) Vaughn: "Re: Vb 6.0 ADO Methodology vs. .NET"
- In reply to: Alex Ackley: "Vb 6.0 ADO Methodology vs. .NET"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
