Hi

I have been developing vb/access but am new to sql server.Is there a sample
vb.net/sql server app somewhere that I can use to pick some pointer on how
to develop sql server apps in vb.net? Any other pointers will also be
appreciated.

Many Thanks

Regards

John,

I think that you should be more precise.

What do you want, develop in a way you did with ms-access
Have you used Jet (often called Access) with VB
What kind of VB did you use.

If the VB was a Net version and the database was Jet, then the only
difference is that you for SQL server better can use the SQLClient provider
instead of OledDB, but that is beside the connection string almost
changeable with Find and Replace (and not use the ? with parameters, as in
SQL those are named)

Cor

"John" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi
>
> I have been developing vb/access but am new to sql server.Is there a
> sample vb.net/sql server app somewhere that I can use to pick some pointer
> on how to develop sql server apps in vb.net? Any other pointers will also
> be appreciated.
>
> Many Thanks
>
> Regards
>

John, there is a LOT more to learning SQL Server over JET/Access development
than changing Connection Strings. I've written several books on the subject
and the ones still available would go a long way to bringing you up to
speed. See my website for more details.

--
__________________________________________________________________________
William R. Vaughn
President and Founder Beta V Corporation
Author, Mentor, Dad, Grandpa
Microsoft MVP
(425) 556-9205 (Pacific time)
Hitchhiker’s Guide to Visual Studio and SQL Server (7th Edition)
http://betav.com http://betav.com/blog/billva
____________________________________________________________________________________________



"John" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi
>
> I have been developing vb/access but am new to sql server.Is there a
> sample vb.net/sql server app somewhere that I can use to pick some pointer
> on how to develop sql server apps in vb.net? Any other pointers will also
> be appreciated.
>
> Many Thanks
>
> Regards
>

The following paper discusses Access/SQL Server in the context of
using Access as a front-end, but it will nevertheless be helpful in
understanding the differences between the two engines, which will be
critical to succeeding on a server-based platform --
http://msdn.microsoft.com/en-us/library/bb188204.aspx. There isn't a
lot of documentation about how Jet works as contrasted with SQL
Server--this is pretty much it. OTOH, there's lots of VB/.NET
resources out there -- good luck with the project ;-)

--Mary

On Wed, 13 May 2009 02:13:25 +0100, "John" <(E-Mail Removed)>
wrote:

>Hi
>
>I have been developing vb/access but am new to sql server.Is there a sample
>vb.net/sql server app somewhere that I can use to pick some pointer on how
>to develop sql server apps in vb.net? Any other pointers will also be
>appreciated.
>
>Many Thanks
>
>Regards
>

Hi Mary,

Is it really so difficult to go from Access to SQL server.

But Bill and you live in Redmond. There you learn probably first to fly a
spaceshutle before you step on a bicycle and later a car.

Here we have to do it with a scooter.

Cor

Actually, I live in Florida and unlike Bill, I have no corporate jet
much less a space shuttle. Having been MVP from 1995 to 2004 when I
joined msft, I've seen a world of trouble from people who have come to
grief in various migration scenarios, so I can categorically state
with great authority that YES, it really can be quite difficult to go
from Access to SQL Server. They are totally different database
engines, and ignorance is not your friend should you ever have to make
that journey from the desktop to a server RDBMS.

--Mary

On Mon, 18 May 2009 20:01:37 +0200, "Cor Ligthert[MVP]"
<(E-Mail Removed)> wrote:

>Hi Mary,
>
>Is it really so difficult to go from Access to SQL server.
>
>But Bill and you live in Redmond. There you learn probably first to fly a
>spaceshutle before you step on a bicycle and later a car.
>
>Here we have to do it with a scooter.
>
>Cor

Mary Chipman [MSFT] wrote:
> Actually, I live in Florida and unlike Bill, I have no corporate jet
> much less a space shuttle. Having been MVP from 1995 to 2004 when I
> joined msft, I've seen a world of trouble from people who have come to
> grief in various migration scenarios, so I can categorically state
> with great authority that YES, it really can be quite difficult to go
> from Access to SQL Server. They are totally different database
> engines, and ignorance is not your friend should you ever have to make
> that journey from the desktop to a server RDBMS.

+1

Back around 2002/3, we switched from our ACCESS sales database to
Web-Based ODBC/SQL. It was not a piece of cake. :-)

Probably what may it easier was that MySQL had a ACCESS converter
which created schema and *.SQL files. Probably the main reason why
the migration project was pushed.

I'm sure MSSQL has a converter? no?

After that, it was a matter of creation the HTML/GUI access to it -
that more tedious part of the project. I recall (but not the details)
even writing something that recreated the SWITCH menu panels into a
HTML menuing layout. That gave us the project task outline.

If MSQL does not have a converter, you might want to use another tool
to create the schema and definition SQL files, then use that to
adjust/import into MSSQL. But I suspect this is the easy part and a
non-issue.

--

But in many respects ADO.NET abstracts the database engines from us.

All that is needed to understand are standard SQL and learn about procedures
possibly. Maybe years of using DB's has clouded my judgement but having
written Oracle and SQL and My SQL and in my dreary past Access I fail to see
how it is that big a step if you have a good grounding in SQL / SQL DML.

Yes all the stuff under the hood takes time but if you are migrating an
Access DB do you really need to know this? If he was migrating from Access
to oracle I would say he would struggle but Access to SQL Server, yes there
will be a learning curve but the difference in ADO.NET terms should be
minimal.


"Mary Chipman [MSFT]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Actually, I live in Florida and unlike Bill, I have no corporate jet
> much less a space shuttle. Having been MVP from 1995 to 2004 when I
> joined msft, I've seen a world of trouble from people who have come to
> grief in various migration scenarios, so I can categorically state
> with great authority that YES, it really can be quite difficult to go
> from Access to SQL Server. They are totally different database
> engines, and ignorance is not your friend should you ever have to make
> that journey from the desktop to a server RDBMS.
>
> --Mary
>
> On Mon, 18 May 2009 20:01:37 +0200, "Cor Ligthert[MVP]"
> <(E-Mail Removed)> wrote:
>
>>Hi Mary,
>>
>>Is it really so difficult to go from Access to SQL server.
>>
>>But Bill and you live in Redmond. There you learn probably first to fly a
>>spaceshutle before you step on a bicycle and later a car.
>>
>>Here we have to do it with a scooter.
>>
>>Cor

The relational engine may be abstracted away from the programmability
layer, but it's still there, and if you don't have a good grounding in
relational engine fundamentals (which is not a requirement for using
Access successfully), then you are guaranteed to encounter
difficulties if your application is at all complex or problematical. A
straight port of a failed Access app is almost guaranteed to be worse
in SQL Server when server and network overhead is added to the mix. So
I'd say that migrating may be no big deal for a person such as
yourself who does know their way around the block, but you are by no
means in the majority of people who post to the newsgroups on the
subject ;-)

--Mary

On Wed, 27 May 2009 12:57:07 +0100, "Paul"
<(E-Mail Removed)> wrote:

>But in many respects ADO.NET abstracts the database engines from us.
>
>All that is needed to understand are standard SQL and learn about procedures
>possibly. Maybe years of using DB's has clouded my judgement but having
>written Oracle and SQL and My SQL and in my dreary past Access I fail to see
>how it is that big a step if you have a good grounding in SQL / SQL DML.
>
>Yes all the stuff under the hood takes time but if you are migrating an
>Access DB do you really need to know this? If he was migrating from Access
>to oracle I would say he would struggle but Access to SQL Server, yes there
>will be a learning curve but the difference in ADO.NET terms should be
>minimal.
>
>
>"Mary Chipman [MSFT]" <(E-Mail Removed)> wrote in message
>news:(E-Mail Removed)...
>> Actually, I live in Florida and unlike Bill, I have no corporate jet
>> much less a space shuttle. Having been MVP from 1995 to 2004 when I
>> joined msft, I've seen a world of trouble from people who have come to
>> grief in various migration scenarios, so I can categorically state
>> with great authority that YES, it really can be quite difficult to go
>> from Access to SQL Server. They are totally different database
>> engines, and ignorance is not your friend should you ever have to make
>> that journey from the desktop to a server RDBMS.
>>
>> --Mary
>>
>> On Mon, 18 May 2009 20:01:37 +0200, "Cor Ligthert[MVP]"
>> <(E-Mail Removed)> wrote:
>>
>>>Hi Mary,
>>>
>>>Is it really so difficult to go from Access to SQL server.
>>>
>>>But Bill and you live in Redmond. There you learn probably first to fly a
>>>spaceshutle before you step on a bicycle and later a car.
>>>
>>>Here we have to do it with a scooter.
>>>
>>>Cor
>

Do you even know what ADO.NET is? I hope you're not referring to
"hacks" like Linq, MVC framework, and any guaranteed to fail
RAD techniques.
Get a book on application architecture and design patterns.

On May 27, 7:57*am, "Paul" <paulri...@novareconsulting.com> wrote:
> But in many respects ADO.NET abstracts the database engines from us.
>
> All that is needed to understand are standard SQL and learn about procedures
> possibly. Maybe years of using DB's has clouded my judgement but having
> written Oracle and SQL and My SQL and in my dreary past Access I fail to see
> how it is that big a step if you have a good grounding in SQL / SQL DML.
>
> Yes all the stuff under the hood takes time but if you are migrating an
> Access DB do you really need to know this? If he was migrating from Access
> to oracle I would say he would struggle but Access to SQL Server, yes there
> will be a learning curve but the difference in ADO.NET terms should be
> minimal.
>
> "Mary Chipman [MSFT]" <mc...@online.microsoft.com> wrote in messagenews:(E-Mail Removed)...
>
> > Actually, I live in Florida and unlike Bill, I have no corporate jet
> > much less a space shuttle. Having been MVP from 1995 to 2004 when I
> > joined msft, I've seen a world of trouble from people who have come to
> > grief in various migration scenarios, so I can categorically state
> > with great authority that YES, it really can be quite difficult to go
> > from Access to SQL Server. They are totally different database
> > engines, and ignorance is not your friend should you ever have to make
> > that journey from the desktop to a server RDBMS.
>
> > --Mary
>
> > On Mon, 18 May 2009 20:01:37 +0200, "Cor Ligthert[MVP]"
> > <Notmyfirstn...@planet.nl> wrote:
>
> >>Hi Mary,
>
> >>Is it really so difficult to go from Access to SQL server.
>
> >>But Bill and you live in Redmond. There you learn probably first to flya
> >>spaceshutle before you step on a bicycle and later a car.
>
> >>Here we have to do it with a scooter.
>
> >>Cor