Marcus, Scott (GEAE, RHI Consulting)
scott.marcus at ae.ge.com
Mon Apr 14 08:25:09 CDT 2003
Bill, There are some things that can happen. 1)A user could lock out others users if the FE is opened exclusively. 2)If a user's machine crashes during using the FE, it could lock everyone out of the database (by corruption or otherwise). This method also increases network traffic. 3)If you make temp queries and tables in the FE, you have to worry about collisions when multiple users run the same process. I think that covers most of the bad stuff. Scott -----Original Message----- From: Bill Morrill [mailto:bmorrill at attbi.com] 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