porting Access to SQL Server --- what to do with the front-end?

#41

Thanks David, this makes things a lot easier for me as I am not
experienced with these technical processes

Just to clarify:

For almost any query that I run in the front end Access db on SQL
Server linked tables, the instructions (I presume SQL string) will go
to SQL Server and have JET or SQL Server run the query on the server
and then only the data required will be sent down the line back to the
PC.

Regards
Kevin

#42

On Mar 26, 10:54*pm, "David W. Fenton" <XXXuse... (AT) dfenton (DOT) com.invalid>
wrote:

Quote:

kev... (AT) gmail (DOT) com wrote innews:ea8d7f22-a1f5-4ae4-a7c3-e65033f7e2fe (AT) n7g2000prc (DOT) googlegroups.com
:

For almost any query that I run in the front end Access db on SQL
Server linked tables, the instructions (I presume SQL string) will
go to SQL Server and have JET or SQL Server run the query on the
server and then only the data required will be sent down the line
back to the PC.

Jet doesn't have anything to do with the server side of things --
Jet runs on your local PC. With a Jet back end, all processing is
done in your local PC's memory, but because it loads metadata about
indexes and other internal structures in the MDB file on the file
server, its requests to the file system on the server are very
efficient. With a server database on the other end, Jet basically
hands off to the server any commands it knows that server can
process itself.

So, in general, the approach is:

Write plain old SQL running on linked tables.

90% of the time or more, it will be very efficient, and hand
everything off to the server (or almost everything -- not enough to
be inefficient). The other 10% of the time, you may have to move
some parts of the process to the server, or use passthrough queries
(which Jet doesn't touch at all).

Thanks David, for bravely leading us forward to the twentieth century.

I thought it was ODBC that did those interpetative tasks?. Oh wait, I
see that they're successful only 90% of the time, so I guess it must
be JET?

As you know, I've been a fan of JET since I realized it had been
talked about in Revelations:
"And I looked, and behold a pale horse: and his name that sat on him
was Death, and Hell followed with him."

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

porting Access to SQL Server --- what to do with the front-end?

comp.databases.ms-access comp.databases.ms-access

Re: porting Access to SQL Server --- what to do with the front-end? - 03-26-2009 , 04:23 PM

Re: porting Access to SQL Server --- what to do with the front-end? - 03-27-2009 , 01:41 AM