G
Guest
Hello,
I have been trying to migrate my Access Application built in Access 2003
onto SQL Server, but for many of the forms I use Domain Aggregate Functions
(DAFs). I am still keeping my front end as Access but the back end process is
SQL 2000. I decided to use ODBC linked tables instead of an Access Project as
it is easier to upsize the backend (to SQL Server 2005). At the moment the
volume of data is reasonably small, but it is expected to increase
expotentially, so I need to minimise potential performance issues.
Does anybody know what the inner workings of these functions with ODBC
tables...do they do a full table scan before executing a select, or another
aggregate query, or is the processing done on the server side?
Do DAFs form an independent connection to the linked table each time you
call them?
Is using an ADO connection object faster and less resource intensive than
DAFs?
I have been trying to migrate my Access Application built in Access 2003
onto SQL Server, but for many of the forms I use Domain Aggregate Functions
(DAFs). I am still keeping my front end as Access but the back end process is
SQL 2000. I decided to use ODBC linked tables instead of an Access Project as
it is easier to upsize the backend (to SQL Server 2005). At the moment the
volume of data is reasonably small, but it is expected to increase
expotentially, so I need to minimise potential performance issues.
Does anybody know what the inner workings of these functions with ODBC
tables...do they do a full table scan before executing a select, or another
aggregate query, or is the processing done on the server side?
Do DAFs form an independent connection to the linked table each time you
call them?
Is using an ADO connection object faster and less resource intensive than
DAFs?