Not to dispute anything, but let me establish my position: I am an
enterprise programmer by trade, although I started out with Access but
have moved on (well, expanded my horizons). Access is not an Enterprise
tool. Visual Studio 2005 Enterprise is an enterprise tool. Sql Server
is an enterprise tool. I am responding to users who try to use Access
in the enterprise environment. If you are going to be doing enterprise
level programming - you should use an enterprise level tool like VS 2005
enterprise (or VS professional). But as long as people are going to try
to use Access in an Enterprise environment, I am just sharing my
experiences with that.
I spent a few years with ADP's - which are ODBC based - continuous
connections. I had more problems with that than I did using an MDB with
ADO and sql server.
For non enterprise operations and a sql server back end, ODBC is fine
with Access. But once you get more than one user using the application
at the same time - you are migrating into enterprise country and will
have the issues that is being posted about here.
Access is a great tool when used in its element (non enterprise). But
with time, everything is migrating to enterprise operations for which
Access was not really designed. Thus, enterprise tools like VS 2005
have been developed (by the same company - Microsoft).
For a non enterprise tool, Access has remarkable capabilities. But for
hard core enterprise operations, there just isn't any getting around
using an enterprise tool like .Net or Java.
Example: this week I had to create a custom graphical search program to
search harddisks for various files and open them (to validate records on
a sql server...interface with the sql server...). The program uses
delegates, interfaces, and .Net 2.0 framework GUI controls, ADO.Net. I
probably could write the code part in Access with a bunch of API's, but
I would not be able to use the GUI controls from the .Net framework
because Access is not .Net compatible. Even so, it would have been much
harder to implement the API's in Access (and a ton more code) than to
create this thing in .Net.
I share my com experience with the Access crowd because people shared
their experience with me when I was starting out, and it also keeps me
up to speed on new developments in com/Access. But for the folks who
need to do more than Access was designed for, I share my experience
their also. Obviously you can't use ADO.Net with Access, and I really
don't see why people say that ADO is dead. It may not have the
capabilties of ADO.Net, but it has way more capabilities than ODBC for
those people who need to use Access in an Enterprise setting.
If this thread is not about enterprise operations and Access, then my
discussion is pretty moot.
Rich
*** Sent via Developersdex
http://www.developersdex.com ***