Susan Geller
sgeller at cce.umn.edu
Tue Aug 26 11:58:30 CDT 2003
To have the best performance you'll want to use an ADP and stored procedures. Part of the benefit is in the sprocs which do all the processing on the server side and are efficient in and of themselves (if designed correctly). --Susan -----Original Message----- From: Stephen R. Zayko [mailto:szayko at secor.com] Sent: Tuesday, August 26, 2003 7:56 AM To: 'Access Developers discussion and problem solving' Subject: RE: [AccessD] SQL_Svr BE Access FE-adp Another question to toss into the mix: How does the adp setup handle the whole client-side / server-side of processing? If the FE is querying medium sized tables (1e4=>1e6 records) does it pass the whole table across the connection (for the client machine to process) or does the SQL Server process the data before transmitting it? -Stephen -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Haslett, Andrew Sent: Monday, August 25, 2003 09:36 PM To: 'Access Developers discussion and problem solving' Subject: RE: [AccessD] SQL_Svr BE Access FE If you're starting from scratch then an ADP will offer the best performance. You will need to use ADO to interact with the BE which may be a drawback if you are used to DAO. If you already have a front-end then ODBC links may be the best option as it will require very little alteration of existing code / queries etc. You're third option is *basically* what an ADP does, in that it makes ADO calls to SQL Server when required. When you say 'live on the internet' are you talking about your SS BE? If so, then perhaps a web-based front end will offer the best solution. Who are your clients? Where will they be accessing it from? Are you distributing the FE to numerous locations? etc. Cheers, Andrew -----Original Message----- From: Stephen R. Zayko [mailto:szayko at secor.com] Sent: Tuesday, 26 August 2003 10:26 AM To: 'Access Developers discussion and problem solving' Subject: [AccessD] SQL_Svr BE Access FE Dear group: I was wondering if I could get some input for the following scenario: I am writing an AccessXP FE for a MS_SQL Server database that will live on the internet. I was wondering how would be the best way to connect to the data (only I can TRULY answer this question)? But in asking myself that, I was wondering what the pros and cons of each of these are and if anyone has strong feelings one way or another on these: 1) Linked tables via ODBC (using system DSN) 2) Write the FE as an .adp with tables directly connected to server tables 3) Call all connections on the fly to the server where the BE is located 4) Some other way that I do not know about. Most users will have an DSL or T1 connection to the internet. Thanks in advance for your inputs. -Stephen Zayko _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com IMPORTANT - PLEASE READ ******************** This email and any files transmitted with it are confidential and may contain information protected by law from disclosure. If you have received this message in error, please notify the sender immediately and delete this email from your system. No warranty is given that this email or files, if attached to this email, are free from computer viruses or other defects. They are provided on the basis the user assumes all responsibility for loss, damage or consequence resulting directly or indirectly from their use, whether caused by the negligence of the sender or not. _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com