Re: Access or Visual Studio?
I agree with you, Access is ideal for many scenarios. There is nothing wrong
with the tool itself (at least the client IDE/reporting/querying part, i
think there are a number of issues with using it as a backend DB, but even
those may not matter depending on your needs).
It seems to me that the Access vs. VS.NET "argument" is between two equally
valid and effective toolsets, just different paradigms re: deployments and
thick vs. thin client. In that light it is silly to point to one paradigm or
another as "not being a serious development environment".
-idi_amin
"SusanV" wrote:[color=blue]
> Thanks for the clarification, but can one simply learn as they go in .NET?
> I've got some VB.Net and some C++, but both of those were VERY difficult to
> learn - never mind actually put into real-world use. Access may not be the
> be-all-end-all, but pretty much anyone with half a brain can at least learn
> by doing, and it sure beats nothing at all. IMHO for a small office it's
> ideal, especially when resources for software, hardware, training and
> support are minimal.
>
> Just my 2 cents...
>
> Susan[/color]
I agree with you, Access is ideal for many scenarios. There is nothing wrong
with the tool itself (at least the client IDE/reporting/querying part, i
think there are a number of issues with using it as a backend DB, but even
those may not matter depending on your needs).
It seems to me that the Access vs. VS.NET "argument" is between two equally
valid and effective toolsets, just different paradigms re: deployments and
thick vs. thin client. In that light it is silly to point to one paradigm or
another as "not being a serious development environment".
-idi_amin
"SusanV" wrote:[color=blue]
> Thanks for the clarification, but can one simply learn as they go in .NET?
> I've got some VB.Net and some C++, but both of those were VERY difficult to
> learn - never mind actually put into real-world use. Access may not be the
> be-all-end-all, but pretty much anyone with half a brain can at least learn
> by doing, and it sure beats nothing at all. IMHO for a small office it's
> ideal, especially when resources for software, hardware, training and
> support are minimal.
>
> Just my 2 cents...
>
> Susan[/color]
Comment