Bobby Heid
bheid at appdevgrp.com
Fri Mar 24 09:50:10 CST 2006
Hi Phil, Comments in-line. Bobby -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Phil Huisman Sent: Friday, March 24, 2006 10:01 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Access help needed by my brother's friend Bobby, >Thank you for the information. I noticed there is a wizard for splitting the database, which I tried and >it successfully created a BE database with only the tables. What confused me is the original DB still >has the tables in it. I kind of expected the tables to be removed when the BE was created. So, does >that mean I need to manually create another DB with only the forms, queries, etc. for the FE? Assuming that what was left in the FE are not links to the BE (the linked tables have a little arrow to the left of the table name (at least in list view)), you should be able to just delete the existing tables that are in the FE db. I always design my systems with a FE/BE design, so I have not ever had to split one. >Once I have a FE without tables and the BE with only tables, the BE >resides on the host computer and the FE is distributes to the other >PC's on the network? That is correct. >To distribute the FE do I simply copy the same >FE DB to the other PC's on the network? Yes, assuming that the other PCs have Access on them. Note that you should be compiling the FE and giving the MDE to the users. >Is the linking routine done from the host PC that has the BE DB >or from the other PC's that have the FE DB? Or does it matter? The links will be in the FE - linking to the BE tables. >Once all of this is accomplished, will multiple PC's be able to >update the BE DB simultaneously, assuming they are not updating >the same record? Theoretically yes. It depends on how the system was designed. You will really just have to test it out to be sure. >I hope this makes sense. >Phil ----- Original Message ----- From: Bobby Heid<mailto:bheid at appdevgrp.com> To: 'Access Developers discussion and problem solving'<mailto:accessd at databaseadvisors.com> ; 'Phil Huisman'<mailto:pbhuisman at msn.com> Sent: Thursday, March 23, 2006 5:12 AM Subject: Re: [AccessD] Access help needed by my brother's friend Phil, I am assuming that you have the forms/code and the tables in one database. You need to split the database into a front-end (FE) and back-end (BE). That is, you have a database that only contains the data (tables) and another database that has all of the code/forms/reports/etc. in it. You link to the tables in the BE from the FE by going to File/Get External Data/Link tables and then locating the BE and selecting all of the tables that you want to be linked to the FE. Then you put the BE in one place and distribute the FE to all of the users. Without going into a lot of detail about auto-linking the tables, you should link the tables in each FE database to the one BE database. Hope this helps, Bobby -----Original Message----- From: accessd-bounces at databaseadvisors.com<mailto:accessd-bounces at databaseadvisors .com> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Kathryn Bassett Sent: Wednesday, March 22, 2006 2:06 PM To: 'Phil Huisman'; 'Access Developers discussion and problem solving' Subject: [AccessD] Access help needed by my brother's friend Phil, I'm forwarding your message to a list called AccessD run by DataBaseAdvisors http://www.databaseadvisors.com/lists/whatandhow.htm<http://www.databaseadvi sors.com/lists/whatandhow.htm> as the scope of your request is beyond my skills. I highly recommend you join the list right away to see answers from people who reply to the list instead of directly to you. I'm positive someone will be able to help you. -- Kathryn Rhinehart Bassett (Pasadena CA) "Genealogy is my bag" "GH is my soap" kathryn at bassett.net<mailto:kathryn at bassett.net> http://bassett.net<http://bassett.net/> -----Original Message----- From: Phil Huisman [mailto:pbhuisman at msn.com] Sent: 21 Mar 2006 7:02 am To: kathryn at bassett.net<mailto:kathryn at bassett.net> Subject: Ken Rhinehart My name is Phil Huisman and your brother Ken gave me your name as a possible contact for help with Microsoft Access. I recently developed an Access database program for a ministry I am involved with at Glenkirk Church called Shepherd's Pantry. We need a DB to track people we serve so I decided to give it a try. After some struggling, I have managed to create a DB I think will meet our needs but there is one problem: we have a network of three PC's at the Pantry and the DB cannot be updated by all three PC's. I did manage to get all three PC's to share the DB but only in the 'read only' mode. Any changes to the database on PC's 2 or 3 cannot be saved? We get an error message but I forget exactly what the message says. I am using Microsoft Office 2003 Access, and XP Home operating system on new Dell PC's. The three PC's are networked together through a Linksys router. I take it we cannot just use standard Access in a network and be able to update the database from multiple PC's? It occurred to me we made need to have a dedicated server running Windows NT or something like that? Anyway, I hope this makes sense and would certainly appreciate any help you can provide. Thank you, Phil Huisman