P
(PeteCresswell)
Let's say we have an MS Access form with a half-dozen subforms.
Parent record gets displayed on part of the form and various
lists of child records are on the six subforms.
Now, for the sake of argument; let's say there's a good reason
for the parent and subform's not being hooked directly into the
back-end tables and therefore, they will be based on work tables.
The question: is it more efficient to make whose work tables
#Temp tables in in an SQL Server DB or make them DAO tables in a
JET work DB in, say, C:\Temp?
My current rationalization favors JET tables in C:/Temp.
Reason: the information for all seven tables (parent plus six
child tables) has to make the trip across the LAN from SQL Server
to the app one way or another, so the number of bits seems tb a
wash.
But by using DAO/JET tables locally, I can open up a single ADO
connection, get all the information for all the tables in a
single stream and the break it up into the respective JET tables
in C:\Temp. One-stop shopping, so-to-speak.
OTOH, using #Temp tables in SQL Server, I'm not only loading up
the server, but I'm also conducting seven separate connections.
Am I on the right track with this? Or is there some flaw in my
reasoning?
Parent record gets displayed on part of the form and various
lists of child records are on the six subforms.
Now, for the sake of argument; let's say there's a good reason
for the parent and subform's not being hooked directly into the
back-end tables and therefore, they will be based on work tables.
The question: is it more efficient to make whose work tables
#Temp tables in in an SQL Server DB or make them DAO tables in a
JET work DB in, say, C:\Temp?
My current rationalization favors JET tables in C:/Temp.
Reason: the information for all seven tables (parent plus six
child tables) has to make the trip across the LAN from SQL Server
to the app one way or another, so the number of bits seems tb a
wash.
But by using DAO/JET tables locally, I can open up a single ADO
connection, get all the information for all the tables in a
single stream and the break it up into the respective JET tables
in C:\Temp. One-stop shopping, so-to-speak.
OTOH, using #Temp tables in SQL Server, I'm not only loading up
the server, but I'm also conducting seven separate connections.
Am I on the right track with this? Or is there some flaw in my
reasoning?