[dba-Tech] Access vs. .NET

Shamil,

I'm using VS.NET 2003. It's part of that nifty Microsoft ISV Empower program: the entire MSDN Universal subscription for $375. I think...yes. VS 2005 Beta is on the DVD set, too, but I'm not going to mess with it while I've got a deadline looming over me.

I just got an AMD 64 system with a GB of RAM, so the IDE is pretty quick.

I can well believe that you find VS.NET as RAD as Access. Like, you're a development god! I'm an intelligent guy but it takes a while for my synaptical engrams to reach a critical mass of understanding, where everything starts to fall comfortably into place. I am simply not comfortable yet.

I am, indeed, working on a professional project, but the deadline is approaching. It's a conversion of an existing Access application (that I also wrote) that stores industrial ergonomic data on factory worker's jobs complete with pictures showing job stresses. The Access program uses replication to keep everybody in synch. The switch to a SQL Server back end on the GoreNet will be a definite improvement.

The Help? Sheesh! I posted a message about using the help to scan through and count all the entries that begin with the word "data." Over 5,600 entries in the index, fer cry-yi! I'm having a bit more luck with the books I've purchased and with Google searches, while visiting the usual web resources: 4Guys, SQL Server Central, etc.

I'm sure I'll be fine with it pretty soon. This is simply deadline angst and I've got nobody else to cry to.

Steve Erbach
Neenah, WI

> ------------Original Message------------
> From: Shamil Salakhetdinov <shamil at users.mns.ru>
> To: "Discussion of Hardware and Software issues" <dba-tech at databaseadvisors.com>
> Date: Wed, Nov-17-2004 4:37 PM
> Subject: Re: [dba-Tech] Access vs. .NET
> 
> Steven,
> 
> What VS.NET version do you use and what is your PC?
> I've found VS.NET 2003 as RAD as MS Access or even more...
> For professional programming of course not for making toys...
> They say that VS.NET 2005 is outstanding comparing it with VS.NET 2003.
> I haven't yet seen/touced VS.NET 2005...
> 
> > It ain't quite that bad but I've never had to buy so many
> >  reference books and have them open at the same time.
> Why not use VS.NET's dynamic help with MSDN.NET?
> 
> > Anybody else with a less florid description of .NET development?
> I think as soon as you get comfortable with VS.NET you'll change your
> opinion about  it...
> 
> Shamil