Hi John,
One of the option is to have VBA code to allow the App's administrator to update the txt file when necessary. This will prevent the access to and modify the location and name of the BE mdb in the VBA code.
Regards,
Thomas
--- In MS_Access_Professionals@yahoogroups.com, John Viescas <JohnV@...> wrote:
>
> Thomas-
>
> Sure, you could put the location in a text file, but then how do you keep the
> text file updated?
>
> John Viescas, author
> Microsoft Office Access 2010 Inside Out
> Microsoft Office Access 2007 Inside Out
> Building Microsoft Access Applications
> Microsoft Office Access 2003 Inside Out
> SQL Queries for Mere Mortals
> http://www.viescas.com/
> (Paris, France)
>
>
>
> -----Original Message-----
> From: MS_Access_Professionals@yahoogroups.com
> [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of Thomas
> Sent: Friday, August 24, 2012 7:20 PM
> To: MS_Access_Professionals@yahoogroups.com
> Subject: Re: [MS_AccessPros] Copy/import tables between 2 DBS
>
> Hi John,
>
> Thanks for your response.
>
> I hate to muddle with the registry and avoid prompting the end user to enter the
> location of the BE. The copy/import should be hidden from the user. It should be
> transparent to them.
>
> One option is externalize the location of the BE to a text file. The VBA code
> can then read the file, get the location of the BE and then import/copy the
> file. That way, if the BE is moved to a new location, the text file will be
> updated making it transparent. Of course, if there are linked tables, it will
> have to be relinked.
>
> I do have codes in place to prompt if a relink is required. This operation is
> only performed by someone who knows what s/he is doing.
>
> I welcome your thoughts/suggestions.
>
> Thanks,
> Thomas
>
>
>
> --- In MS_Access_Professionals@yahoogroups.com, John Viescas <JohnV@> wrote:
> >
> > Thomas-
> >
> > Can you explain what you mean by "need to have a cut off between the 2 apps?"
> >
> > Yes, you could put the file name in a file or a Registry entry, but that's
> still
> > "hard coded" in a way. You could also prompt the user for the file location
> via
> > the Windows File Dialog.
> >
> > Can I assume user "B" (the user needing the update) can access the files for
> > user "A" over the network? That would definitely be a requirement.
> >
> > You could write code behind a button that user "B" clicks to prompt for the
> file
> > location, then link to the other file dynamically and import / refresh the
> data.
> > If you're updating local tables in user "B" database, then the best way would
> be
> > to temporarily link to the external tables one at a time, run queries to
> perform
> > the update, then delete the link. This can all be done in VBA code, but I
> need
> > more details.
> >
> > John Viescas, author
> > Microsoft Office Access 2010 Inside Out
> > Microsoft Office Access 2007 Inside Out
> > Building Microsoft Access Applications
> > Microsoft Office Access 2003 Inside Out
> > SQL Queries for Mere Mortals
> > http://www.viescas.com/
> > (Paris, France)
> >
> >
> >
> >
> > -----Original Message-----
> > From: MS_Access_Professionals@yahoogroups.com
> > [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of Thomas
> > Sent: Wednesday, August 22, 2012 10:19 PM
> > To: MS_Access_Professionals@yahoogroups.com
> > Subject: Re: [MS_AccessPros] Copy/import tables between 2 DBS
> >
> > No, the tables are not linked table.
> >
> > I agree with you that sharing a BE mdb is an option. However, there is a need
> to
> > have a cut off between the 2 apps. Hence, the need to import/copy.
> >
> > I imagine I can include a checking to ensure the tables are sync up. If not,
> > refresh it on the fly before users start to use the app which use the table as
> > an input source.
> >
> > Then my next question is how to externalize the location of the remote db to a
> > file to avoid hard coding it.
> >
> > Regards,
> > Thomas
> >
> > --- In MS_Access_Professionals@yahoogroups.com, John Viescas <JohnV@> wrote:
> > >
> > > Thomas-
> > >
> > > Is using linked tables an option? Why not have both front ends point to the
> > > same shared back end?
> > >
> > > John Viescas, author
> > > Microsoft Office Access 2010 Inside Out
> > > Microsoft Office Access 2007 Inside Out
> > > Building Microsoft Access Applications
> > > Microsoft Office Access 2003 Inside Out
> > > SQL Queries for Mere Mortals
> > > http://www.viescas.com/
> > > (Paris, France)
> > >
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: MS_Access_Professionals@yahoogroups.com
> > > [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of Thomas
> > > Sent: Wednesday, August 22, 2012 7:28 AM
> > > To: MS_Access_Professionals@yahoogroups.com
> > > Subject: [MS_AccessPros] Copy/import tables between 2 DBS
> > >
> > > I would like to seek recommendations from the experts the best approach to
> > > import/Copy tables btw 2 access DBs.
> > >
> > > The reason is the tables are being updated by one db and then used by the
> > other
> > > as input/inquiry on a daily basis.
> > >
> > > Your recommendations are always much appreciated.
> > >
> > > Thank you.
> > >
> > > Thomas
> > >
> > >
> > >
> > >
> > >
> > > ------------------------------------
> > >
> > > Yahoo! Groups Links
> > >
> >
> >
> >
> >
> > ------------------------------------
> >
> > Yahoo! Groups Links
> >
>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
Tidak ada komentar:
Posting Komentar