I found that by defining an ADO connection to my back end database, I can
execute a SQL query stored in my back end database.
The query is stored in the back end database..but runs on YOUR computer. You
did not intstall ado, or jet, or any kind of database software where the
back end database resides. You are running the software on YOUR computer.
That file is just a plain old file. If you open Excel, then all processing
and running of the software occurs on your pc. If you open a mdb file...once
again just like Excel...all processing occurs on your pc.
So, that query does NOT get exected on the back end.. The qeury is read into
your local pc memory..and then execuedin on YOUR pc.
Has anyone used this technique and is it any more or less efficient than
storing the queries in the local database?
Well, actaully it is less efficint. If you ahve a split arramnt..then all
the code, querys etc. resides on YOUR pc. And, then when it comes time to
load the sql into memory to execute..you will not be draggin the sql accorss
the netwrok.
I figured If i put all my tables and queries in the back end, I can do
away with my table links and use the ADO connection to connect and
disconnect thus not maintaining any connection to my back end except when I
need it.
But why is having a connection a problem? You essentially have no limits in
this regards anyway. What advantage do you get by not having a connection
open?
But...to put this in perspective...no..it is a dumb idea...and gains you
nothing....