| | |
|
|
|
Processing |
|---|
| message from =?Utf-8?B?TWFyZ2U=?= on 1 Jun 2004 |
I have created and Access adp using a SQL Server backend. I know the queries are processed by the Server but what about the code behind the forms ? where is this processed my guess is client side. If so should I be using queries where possible and just using the RunSql command from the forms or how should I optomise performance.?
|
| Graham R Seach replied to =?Utf-8?B?TWFyZ2U=?= on 2 Jun 2004 |
Marge,
VBA code is executed on the client. VBA is intended to provide
functionality, whereas SQL is intended to provide data manipulation. Of
course, VBA (through DAO and ADO) gives you access to the many data
manipulation methods which you can then use to execute SQL.
SQL executed on the server will always run faster than cursor methods
(looping through recordsets), so my advice is to use whichever method you
feel is most appropriate, depending on what you're doing at the time.
Regards,
Graham R Seach
Microsoft Access MVP
Sydney, Australia
Microsoft Access 2003 VBA Programmer's Reference
http://www.wiley.com/WileyCDA/WileyTitle/productCd-0764559036.html
"Marge" <anonymous@discussions.microsoft.com> wrote in message
news:95FC774B-7792-430C-811A-67CEEB5F3FEC@microsoft.com...
queries are processed by the Server but what about the code behind the forms
? where is this processed my guess is client side. If so should I be using
queries where possible and just using the RunSql command from the forms or
how should I optomise performance.?
|
|
Archived message: Processing (Microsoft Access Error Message)
