I assume you are talking about VB.Net and Windows forms. I'm not sure why
you think that it's only for quick and dirty jobs, it's pretty powerful,
although a pig to learn. My dislike for VB.Net (and Visual Studio) is such
that I have recently been experimenting with Delphi, although I haven't gone
far enough yet to be able to recommend it.

If you are mainly using unbound forms, forget about Access. Using Access to
build unbound forms is like taking a sledgehammer to crack a nut. However,
I am curious as to the circumstances in which you feel you need to go
unbound. It is rarely necessary in my experience.

"PMK" wrote in message
...
I just wonder if I am wasting my time learning VS 2005.

I've developed in Access for a long time, and seek out advanced work
which invariably requires complex unbound data entry forms connected
to a MS SQL back end.

Taking a hard look and experimenting with dotnet 2.0 and Visual Studio
2005 to see if dotnet Windows forms might be a good alternative for
these specific kinds of jobs, so far it doesn't seem so. My impression
thus far is it's great for quick and dirty jobs, but not complex ones.

What do you guys think? Better to stay with Access and SQL Server or
not?

Peter