Mike and Doris Manning
mikedorism at ntelos.net
Mon Apr 14 09:43:41 CDT 2003
Another drawback is that you won't be able to take exclusive control of the network FE when changes are needed. You'll have to wait for all the users to get out of the database or have a way to kick them out. Doris Manning Database Administrator Hargrove Inc. www.hargroveinc.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Bill Morrill Sent: Monday, April 14, 2003 9:14 AM To: AccessD at databaseadvisors.com Subject: [Accessd] FE/BE on server vs FE on workstation/BE on server? 4-14-03 For sometime I have been putting frontends(forms, queries, reports etc) on workstation machines and backends(tables) on server. Links would then be made from each workstation to the server. Recently, a user mentioned that they were using the same database frontend/backend on the server. Each user would activate the frontend on the server and then the backend on the server would of course be linked to the frontend. They said this shared backend/frontend situation worked fine and that there was no need to put the frontend on each workstation. Anyone know the ramifications for this frontend/backend on server idea? Does this impact the network performance? Does this reduce the maximum number of concurrent users? Would Access have to be installed on the server to make this viable? Thanks in advance, Bill _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com