Heenan, Lambert
Lambert.Heenan at AIG.com
Tue May 20 10:14:58 CDT 2008
Hear hear! -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin at Beach Access Software Sent: Tuesday, May 20, 2008 9:38 AM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Multiple Frontend Users Arthur: That thing about the back up doesn't make sense. The original is on the server. Only COPIES are on the clients. It doesn't need to be backed up at the client end. If a machine gets replaced, a shortcut to the FE on the server would need to be created anyway. Why not just copy the FE from the server to the new client? The answer is simple - control. It's just petty politics. They want to be in control and when you put something on a client you lose control. Yes and MDE would be better so that they don't go mucking around with your objects. But really... Rocky Smolin Beach Access Software 858-259-4334 www.e-z-mrp.com www.bchacc.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Arthur Fuller Sent: Tuesday, May 20, 2008 4:53 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Multiple Frontend Users I was presented with this problem recently and recommended this solution. The network support people flatly refused it. They argued that in their setup (with hundreds of users) virtually nothing on the local PCs was backed up. The local PCs can be replaced and/re-imaged anytime, and users are warned not to store anything locally, otherwise it won't be backed up. So I had no choice but to put both the FE and the BE on a network share. The argument makes perfect sense to me, but I've never done it that way before. What will happen when a hundred users open a single FE? Should I replace the FE MDB with an MDE? Thanks, Arthur On Mon, May 19, 2008 at 10:42 AM, Dan Waters <dwaters at usinternet.com> wrote: > Ed, > > Even with 3 users, splitting is a good preventive measure to avoid > data corruption. You can put the Access Back End .mdb file on the > server, and put the Front end .mdb files on each user's PC. Managing > 3 users shouldn't be difficult. > -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com No virus found in this incoming message. Checked by AVG. Version: 7.5.524 / Virus Database: 269.23.21/1455 - Release Date: 5/19/2008 5:04 PM -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com