Hi Agestha,
I have not heard of the Linking to MySql and mdb BE's
problem. You could raise a new problem so that the
experts in those fields can see the new title and
advise you.
There are a couple of file in the Group_Files that
may be of interest to you for deploying your files to
the users:
BatchFile_SampleFrontEndUpdate.zip
Utilities\LinkToNewBackEnd.zip
Regards, Clive.
--- In MS_Access_Professionals@yahoogroups.com, Agestha Hendra <agesthahendra@...> wrote:
>
> Thanx Clive..
>
> Yes, the secondary tables are updated by each users...
> so because of that i plan to make another BE with access file with secondary tables within and then link them into the FE...
> with that i hope it's not a problem when i have to update the FE...
> what i'm thinking is i'm affraid if the FE have more than one source of link tables (especially if the sources are diffrent type
> example one is Mysql and other is mdb), i've read some articles that it can reduce the performance (i forgot where
> the links/articles are...i tried to browsed again but i could not find them again)...any explanation would be really appreciated
>
> Regards
> Hendra
>
>
>
> ________________________________
> Dari: Clive <zctek@...>
> Kepada: MS_Access_Professionals@yahoogroups.com
> Dikirim: Minggu, 4 Maret 2012 18:39
> Judul: [MS_AccessPros] Re: Link tables from more than one source
>
>
> Â
> Hi Hendra,
>
> Are the secondary tables fixed information or are they
> updatable by the user?
>
> If they are updated by the user, then bear in mind that
> if/when you release an update to the front ends, the
> data in the secondary tables may need to be preserved.
>
> In that is so then you could have secondary tables in a
> back end database on each user's machine, or import the
> secondary tables from the old front end to the new front
> end for each user.
>
> Hope you understand what I am trying to say.
>
> Regards, Clive.
>
> --- In MS_Access_Professionals@yahoogroups.com, "John Viescas" <john@> wrote:
> >
> > Hendra-
> >
> > If the tables will contain data not shared by users, then they should be local
> > tables in each user's copy of the "front end" database. You should not share
> > these on another server.
> >
> > But to answer your question, yes, you can have some linked tables pointing to
> > one database (or server) and others pointing to a different database.
> >
> > 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/
> > (Nashua, NH)
> >
> >
> >
> >
> > -----Original Message-----
> > From: MS_Access_Professionals@yahoogroups.com
> > [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of
> > agesthahendra@
> > Sent: Saturday, March 03, 2012 5:36 PM
> > To: MS_Access_Professionals@yahoogroups.com
> > Subject: [MS_AccessPros] Link tables from more than one source
> >
> > Hi All...
> >
> > Is it okay if our application have more than one source link tables..?
> > I have an application and i plan to use link tables from Mysql on the
> > server...due to several reason, i think it's better to placed several tables
> > that not really important and can be used personally by the users on their local
> > computer (let say secondary tables)....
> > so my plan is make another BE builded with access that contain the secondary
> > tables and placed it on each users computer, and then link its into my FE
> > together with link tables from Mysql...but there are no join between tables from
> > Mysql and tables from Access local BE.
> > Hope my words don't make you get confused...thank you.
> >
> > Regards
> > Hendra
> >
> >
> >
> > ------------------------------------
> >
> > Yahoo! Groups Links
> >
>
>
>
>
> [Non-text portions of this message have been removed]
>
Tidak ada komentar:
Posting Komentar