[AccessD] ACCESS Left Behind

 While that's true to an extent, you just need to understand what's going on
under the hood.

 You can get very acceptable performance just with linked tables, but some
of the features that make Access easy to use will cause you a problem.

 Something as innocent as an IIF() in a query, which many use, and boom,
lousy performance (any Access, VBA, or JET specific expression in a query
forces JET to process the query rather than passing it off to SQL).

Jim. 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mark Simms
Sent: Thursday, January 22, 2015 03:37 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] ACCESS Left Behind

My experience a few years ago: if you used linked tables to SQL Server,
query retrieval times were 2x that of native SQL queries. Updates and
Inserts were up to 10x !!!

Conclusion: you must use stored procs for everything....reports, forms, etc.

> You know what I find most interesting in this whole transition is that
> SQL
> Server Express didn't seem to catch on.
>
> Susan H.


-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com