MarkH
lists at theopg.com
Thu Nov 18 15:32:43 CST 2004
Greg 1) Both mdw files were created independantly and both backends are fully secured (I do have full access on each) 2) I was hoping to avoid merging the workgroups, but if I have to then luckilly one has less than ten users 3) A temporary unsecured database is out of the question unfortunately due to the nature of the data ... I have read, since posting my original message, that the desired result "could" possibly be achieved by creating an access application variable within one of the front-ends that uses a connection string to the other backend which includes workgroup and login details. I would like to avoid this as it seems clumsy, haven't tried it yet though... Looks like merging the two mdw's will be the best bet... Never mind :O) Thanks very much for the suggestions Mark -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Greg Smith Sent: 18 November 2004 20:45 To: accessd at databaseadvisors.com Subject: Re: [AccessD] Accessing data in secured mdb from another secured mdbon a different workgroup Mark: Do any of the groups/users in the two different MDW's have the same PID's? Or were both mdw files created independently? If the latter is true, you might be hosed. I'm ASSuming (dangerous word) that both apps and data sets are using full MS Access security. The next question (or continuing) then, if they both are fully independent, how do you get data from one to the other? You have to somehow combine the mdw's (create new users/groups in one mdw from the other mdw using the PIDs from the other mdw) and then one MDW file would be used for both apps. "Bit of a pain..." is an understatement. I don't know your full setup, but another option would be (warning: this is a cobble...) to create a third UNSECURED db for the data, export data to it from the one database, then import from it into the other database. That way all the exporting and importing is done from the secured db's and they, technically, don't 'see' each other or their security. However, your exported/imported data, while in the unsecured database, is just that...unsecured. You didn't say whether this was a one time deal or an ongoing process, so that may also figure into what you need to do as well. Well, that's MY two cents worth. Good luck! Greg Smith gregsmith at starband.net > Hello All (I sent his yesterday but it didn';t seem to get through...) > > Using AXP on WinXP > > I have two databases secured on different workgroups and accessed from > different front ends. I need to be able to import data from one into > the other but am having problems as they are secured on different > mdw's. I could merge the two mdw's but that would be a bit of a pain. > > Anyone know a simple solution? > > Thanks in advance > > Mark > > -- > _______________________________________________ > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.769 / Virus Database: 516 - Release Date: 24/09/2004 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.769 / Virus Database: 516 - Release Date: 24/09/2004