VB .net

[Paul Ilacqua]

What version of VB .NET do you need to Access a SQL Server database. I
bought VB.Net standard and now it tells me you cannot Access SQL Server.
What's going on?

Paul

[Jon Skeet [C# MVP]]

Paul Ilacqua <Pi******@twcny.rr.com> wrote:

What version of VB .NET do you need to Access a SQL Server database. I
bought VB.Net standard and now it tells me you cannot Access SQL Server.
What's going on?

You certainly *can* access SQL Server - but you may not get the wizards
which make things easier. There's nothing to stop you from writing the
code directly though (things like connection strings, parameters etc
are what get automatically created normally).

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[Paul Ilacqua]

Jon ,
Thanks .. I got a little nervous after sheeling out 100 bucks and going
through a 2 hour installation. I'm a long time VB 4,5,&6, this looks like a
pretty stiff learning curve. It will propbably be 5 years before my company
takes the jump to Dot.NET but I need to be ready. Thanks again.
Paul

"Jon Skeet [C# MVP]" <sk***@pobox.com> wrote in message
news:MP************************@msnews.microsoft.c om...

Paul Ilacqua <Pi******@twcny.rr.com> wrote:

What version of VB .NET do you need to Access a SQL Server database. I
bought VB.Net standard and now it tells me you cannot Access SQL Server.
What's going on?

You certainly *can* access SQL Server - but you may not get the wizards
which make things easier. There's nothing to stop you from writing the
code directly though (things like connection strings, parameters etc
are what get automatically created normally).

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[Steven H]

On Thu, 6 May 2004 18:51:07 -0400, Paul Ilacqua wrote:

Jon ,
Thanks .. I got a little nervous after sheeling out 100 bucks and going
through a 2 hour installation.

painfull isnt it

what i done to speed it up a bit was follow the instructions in the readme
to allow you to do setup over a network.

you just create a few folders copy the cd's into the correct folders edit
setup.ini and your away laughing.

all you need to do is spend 2 minutes selecting install location &
components (there will be a way to avoid this part) and click install.

when i followed that procedure i shaved quite a bit of time off the install
- still too long in my ohh so humble opinion.

i wonder what would happen if some highly paid developers (not me i am just
a student) sent microsoft a bill for time spent installing the development
enviroment - lol.

--
-------------------------------------------
Steven H, 3rd Year B.I.T. Otago Polytechnic

..net Geek

[John Bailo]

Jon Skeet [C# MVP] wrote:

Paul Ilacqua <Pi******@twcny.rr.com> wrote:

What version of VB .NET do you need to Access a SQL Server database. I
bought VB.Net standard and now it tells me you cannot Access SQL Server.
What's going on?

You certainly *can* access SQL Server - but you may not get the wizards
which make things easier. There's nothing to stop you from writing the
code directly though (things like connection strings, parameters etc
are what get automatically created normally).

The SQLClient that is part of the .NET Framework should allow him to access
SQL server from FORTRAN if he wants...But as you say, it might require
native coding, not *wizard* assists....

--
W '04 <:> Open

[Andy Gaskell]

For anyone else that might buy VB.NET Standard Edition -
http://msdn.microsoft.com/vbasic/atthemovies/

"Paul Ilacqua" <Pi******@twcny.rr.com> wrote in message
news:up**************@TK2MSFTNGP09.phx.gbl...

What version of VB .NET do you need to Access a SQL Server database. I
bought VB.Net standard and now it tells me you cannot Access SQL Server.
What's going on?

Paul

[DC]

Steven H wrote:

Jon ,
Thanks .. I got a little nervous after sheeling out 100 bucks and going
through a 2 hour installation.

painfull isnt it
what i done to speed it up a bit was follow the instructions in the readme
to allow you to do setup over a network.

For the various reasons, I had to setup VS.net for a few times on my 'puter.

Practice that works best is:

1.
Copy the CDs to the disk file image (.ISO or .NRG) - I used Nero.

2.
Mount image file as virtual CD drive.

3.
Setup from that.

With this technique I trimmed down installation time to 30%.

LP,
Dejan