[AccessD] Search in AC2007 and SQL-Server

Charlotte Foust charlotte.foust at gmail.com
Mon Nov 15 09:51:22 CST 2010


It isn't straightforward, Mark.  Even using queries in the front end
of a dotnet app will usually be faster than Access because dotnet
developers build them that way.  Optimization happens in dotnet too,
but only the first time the code loads for a particular obect in a
session.  After that, it blazes.  Access will try to optimize on the
fly queries, etc. every time.

As for object orientation vs procedural, ignore that.  Access is
enough object-oriented to get the job done.  With the use of classes,
you come close to what you can do in dotnet.  The rich controls and
secure deployment are the two biggies for dotnet.  Most dotnet
programmers use third party controls that have a wealth of events and
properties that Access can't even come close to, and those controls
integrate into VisualStudio better than any you might use with Access.
 The compiler is built into VisualStudio, so you don't need to jump
through hoops to create a dll or exe.  You still need a good installer
to get it done professionally.  We used InstallShield for that in
dotnet.  The VisualStudio runtime is large, but it's also on most
machines and the installer can be set up to only install it if
required.

Access can be versioned using a source control app like SourceSafe,
but there are more choices with dotnet.  We used SourceGear Vault at
my last employer's, which was enough like sourcesafe to allow us to
hit the ground running, but had a lot of improved capabilities.

Big difference is the learning curve if you aren't already a dotnet
programmer.  You can develop an app faster in Access, but the seams
still won't be tight and the the hull will probably leak a lot. <grin>

Charlotte Foust

On Mon, Nov 15, 2010 at 6:35 AM, Mark Simms <marksimms at verizon.net> wrote:
> What I'm trying to do is compare Access with SQL Server and Dotnet with SQL
> Server for a potential client.
> The big differences vs. dotnet are:
>
> 1) object orientation vs. procedural
> 2) source code versioning
> 3) rich number of GUI controls
> 4) secure deployment (EXE, DLL, etc)
>
> There is no significant issues regarding data retrieval speed when talking
> stored procedures and ADO, correct ?
> IOW, the Access app should be just as fast.
>
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>



More information about the AccessD mailing list