Database Project

[Greg Horwood]

Dear All,

I have been convinced by many that C# is the most appropriate platform to
transform my tiried old Access 2000 applications into a fully fledge seventh
wonder of the world, some of them graduating to MSSQL.

My question (Before I go and learn a new language - VC++ is my usual): Is
the above assertion true? Is C# able to work well with an ADO connection? And
is C# scable, intuative and all the rest.

Any comments really appreciated.

Thanks

Greg

[Frans Bouma [C# MVP]]

Greg Horwood wrote:

Dear All,

I have been convinced by many that C# is the most appropriate platform to
transform my tiried old Access 2000 applications into a fully fledge
seventh wonder of the world, some of them graduating to MSSQL.

My question (Before I go and learn a new language - VC++ is my usual): Is
the above assertion true? Is C# able to work well with an ADO connection?
And is C# scable, intuative and all the rest.

hehe asking in a C# newsgroup if C# is scalable, intuitive and great sounds
like asking in a baptist church if god exists :D.

But seriously: C# is well suited for working with a database through
ADO.NET. It's though more and more common practise that for the lowest layer
in your application, the data access layer, a tool is used to produce this
layer, either by code generation or by for example o/r mapping.

Frans.

--
Get LLBLGen Pro, productive O/R mapping for .NET: http://www.llblgen.com
My .NET Blog: http://weblogs.asp.net/fbouma
Microsoft C# MVP

[Greg Horwood]

Thanks for you reply. Yes, I realise I'm talking to the converted. It's just
that I'm too old to be learning a new language and I'm trying hard to stick
with the tried and tested.

Thanks

Greg

"Frans Bouma [C# MVP]" wrote:

Greg Horwood wrote:

Dear All,

I have been convinced by many that C# is the most appropriate platform to
transform my tiried old Access 2000 applications into a fully fledge
seventh wonder of the world, some of them graduating to MSSQL.

My question (Before I go and learn a new language - VC++ is my usual): Is
the above assertion true? Is C# able to work well with an ADO connection?
And is C# scable, intuative and all the rest.

hehe asking in a C# newsgroup if C# is scalable, intuitive and great sounds
like asking in a baptist church if god exists :D.

But seriously: C# is well suited for working with a database through
ADO.NET. It's though more and more common practise that for the lowest layer
in your application, the data access layer, a tool is used to produce this
layer, either by code generation or by for example o/r mapping.

Frans.

--
Get LLBLGen Pro, productive O/R mapping for .NET: http://www.llblgen.com
My .NET Blog: http://weblogs.asp.net/fbouma
Microsoft C# MVP

[Michael C]

I've written a few SQL Server-connected apps in C#, and for my tastes it
beats the heck out of Access and VBA. There is definitely a learning curve,
but it's well worth it. Just a thought, but for my money the
System.Data.SqlClient seems to work best for SQL Server connections. One
big plus is that you can cheat and use the Access upsizing wizard to
automatically convert your Access DB's to SQL Server (of course you might
want to tweak the resulting SQL DB a little).

Thanks,
Michael C., MCDBA

"Greg Horwood" <Gr*********@discussions.microsoft.com> wrote in message
news:78**********************************@microsof t.com...

Thanks for you reply. Yes, I realise I'm talking to the converted. It's just that I'm too old to be learning a new language and I'm trying hard to stick with the tried and tested.

Thanks

Greg

"Frans Bouma [C# MVP]" wrote:

Greg Horwood wrote:

Dear All,

I have been convinced by many that C# is the most appropriate platform to transform my tiried old Access 2000 applications into a fully fledge
seventh wonder of the world, some of them graduating to MSSQL.

My question (Before I go and learn a new language - VC++ is my usual): Is the above assertion true? Is C# able to work well with an ADO connection? And is C# scable, intuative and all the rest.

hehe asking in a C# newsgroup if C# is scalable, intuitive and great sounds like asking in a baptist church if god exists :D.

But seriously: C# is well suited for working with a database through
ADO.NET. It's though more and more common practise that for the lowest layer in your application, the data access layer, a tool is used to produce this layer, either by code generation or by for example o/r mapping.

Frans.

--
Get LLBLGen Pro, productive O/R mapping for .NET: http://www.llblgen.com
My .NET Blog: http://weblogs.asp.net/fbouma
Microsoft C# MVP

[Robert Schuldenfrei]

Hi Greg,

At 61 years old I too am an old @%#*. I am learning SQL and C# in order to
convert an old COBOL ERP system so as to run in the Windows environment. It
is a hard slog, but it is coming along. At the risk of offending some
computer scientists in this NG, I would suggest you get the following book:
Murach's C#. It uses a bunch of consistent ADO.NET examples to demonstrate
how to do database programming.

Keep us (or at least me) posted on how you are doing.

Cheers,

Bob
--
Robert Schuldenfrei
S. I. Inc.
32 Ridley Road
Dedham, MA 02026
bo*@s-i-inc.com
781/329-4828
"Greg Horwood" <Gr*********@discussions.microsoft.com> wrote in message
news:78**********************************@microsof t.com...

Thanks for you reply. Yes, I realise I'm talking to the converted. It's
just
that I'm too old to be learning a new language and I'm trying hard to
stick
with the tried and tested.

Thanks

Greg

"Frans Bouma [C# MVP]" wrote:

Greg Horwood wrote:

> Dear All,
>
> I have been convinced by many that C# is the most appropriate platform
> to
> transform my tiried old Access 2000 applications into a fully fledge
> seventh wonder of the world, some of them graduating to MSSQL.
>
> My question (Before I go and learn a new language - VC++ is my usual):
> Is
> the above assertion true? Is C# able to work well with an ADO
> connection?
> And is C# scable, intuative and all the rest.

hehe asking in a C# newsgroup if C# is scalable, intuitive and great
sounds
like asking in a baptist church if god exists :D.

But seriously: C# is well suited for working with a database through
ADO.NET. It's though more and more common practise that for the lowest
layer
in your application, the data access layer, a tool is used to produce
this
layer, either by code generation or by for example o/r mapping.

Frans.

--
Get LLBLGen Pro, productive O/R mapping for .NET: http://www.llblgen.com
My .NET Blog: http://weblogs.asp.net/fbouma
Microsoft C# MVP