Help out a friend and get their data back into their newer app? "SRussell" <srussell[ at ]lotmate.com> 31.07.2006 10:53:54 I have been working on a friends app over the week or so and I'm ready to bring it back to him. Of course he and his company have been putting in data in their version of the app. So how do I get their "poo" from their app into my newer version? 20 tables with 2000 rows in a few of the tables, plus a few lookups. TIA

Re: Help out a friend and get their data back into their newer app? "Douglas J. Steele" <NOSPAM_djsteele[ at ]NOSPAM_canada.com> 31.07.2006 11:04:43 To prevent problems like this, the application should be split into a front-end (containing the queries, forms, reports, macros and modules), linked to a back-end (containing the tables and relationships). When you're making changes, you make them to the front-end only. When you're done, you give them a new copy of the front-end, and make sure that it's pointing to the correct back-end. Note that each user should have his/her own copy of the front-end, preferably on his/her hard drive, with only the back-end existing on the server. You can split their existing database now, and only give them the new front-end. References you might find useful for this topic include: http://www.mvps.org/access/tables/tbl0009.htm http://www.granite.ab.ca/access/splitapp/index.htm http://www.granite.ab.ca/access/autofe.htm -- Doug Steele, Microsoft Access MVP http://I.Am/DougSteele (no private e-mails, please) "SRussell" <srussell[ at ]lotmate.com> wrote in message news:%23b4Nf%23ItGHA.1632[ at ]TK2MSFTNGP06.phx.gbl... [Quoted Text] >I have been working on a friends app over the week or so and I'm ready to >bring it back to him. Of course he and his company have been putting in >data in their version of the app. > > So how do I get their "poo" from their app into my newer version? > > 20 tables with 2000 rows in a few of the tables, plus a few lookups. > > TIA >

Re: Help out a friend and get their data back into their newer app? "SRussell" <srussell[ at ]lotmate.com> 31.07.2006 12:48:26 "Douglas J. Steele" <NOSPAM_djsteele[ at ]NOSPAM_canada.com> wrote in message news:OfK3gEJtGHA.2172[ at ]TK2MSFTNGP05.phx.gbl... [Quoted Text] > To prevent problems like this, the application should be split into a > front-end (containing the queries, forms, reports, macros and modules), > linked to a back-end (containing the tables and relationships). When > you're making changes, you make them to the front-end only. When you're > done, you give them a new copy of the front-end, and make sure that it's > pointing to the correct back-end. Note that each user should have his/her > own copy of the front-end, preferably on his/her hard drive, with only the > back-end existing on the server. > > You can split their existing database now, and only give them the new > front-end. > > References you might find useful for this topic include: > > http://www.mvps.org/access/tables/tbl0009.htm > http://www.granite.ab.ca/access/splitapp/index.htm > http://www.granite.ab.ca/access/autofe.htm > Thanks. I'll look into doing this.