[AccessD] Access Queries

There is quite a few developers who imbedded sql code in their FE
applications. If there are numerous people working on a system, the
application is internal to a single small office or people are developing on
"live' SQL BE database, that method may be OK.

To make an application portable I would recommend building your sequel code
as stored procedures and then just pass parameters. It would now not matter
whether your BE is MySQL, MS SQL, Oracle, Postgres and so on particularly as
the SQL is different in each database. So if you decide a new interface (FE)
is needed like ASP.Net or more likely a web FE, it is just an upgrade and
not rebuild. Also note that SPs run significantly faster as they are
pre-optimized/compiled and commonly used SPs are stored in memory. 

I like the idea of keeping the FE and BE as standalone and flexible as
possible.

Jim   

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mark Simms
Sent: Monday, February 20, 2012 8:25 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Access Queries

I'm not a "string SQL" person. I've always thought this was the worst of the
worst features of Access.
I create canned queries and then have a procedure for string replacement ...
Trying to keep everything consolidated into the query catalog.
I never want to be caught saying "now where is that SQL for that query ?"
"Wait ! it's somewhere here in these 10,000 lines of VBA code".


>
> Access routinely changes complex queries as you point out. Why use text
> files though?  Why not vba modules so you can easily see and edit them?


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