Re: Selecting back end(s) to use

From: Douglas J. Steele (NOSPAM_djsteele_at_NOSPAM_canada.com)
Date: 09/08/04 

Date: Wed, 8 Sep 2004 08:09:34 -0400

The BE has no idea what FE is connected to it, so there's nothing that needs
to be done from that perspective.

If you check http://www.mvps.org/access/tables/tbl0009.htm at "The Access
Web", you'll see one approach to relinking BEs.

However, why do you have "a group of identically structured BE's"? That
sounds as though your database may not be properly normalized, and that
you're storing each customer (or region, or product, or whatever) in a
different database. 

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(No private e-mails, please)
"Alp" <esinalp@streamyx.com> wrote in message
news:e6UxnmZlEHA.2020@TK2MSFTNGP09.phx.gbl...
> Hi Experts,
>
> I'm trying to find a solution for the following scenario:
>
> There are several backends for use in the application. This actually is a
> combined reporting application for a group of identically structured BE's.
> Only 2 tables from each BE are used in the FE and each are given aliases
for
> the time being so that they will not interfere with each other.
>
> What I would like to accomplish is that when user selects the BE's he/she
> wants to work with via a form, and only those BE's tables are linked (or
> relinked/reconnected). The reason is not all BE's may be available at
> runtime or user might want to report only on a few BE's.
>
> First, is this possible? (I think it should be, but...)
> Does the FE application has to have aliases already setup for the BE
> databases?
> Would I need to check available BE files within a directory?
> Finally, what would be a better approach to accomplish a selection of
> multiple backends to work with in a frontend?
>
> Too many questions, I know. Any help or guidance will highly be
appreciated.
>
> Thanks in advance.
>
> Alp
>
>
>

Relevant Pages

  • Selecting back end(s) to use
    ... There are several backends for use in the application. ... combined reporting application for a group of identically structured BE's. ... What I would like to accomplish is that when user selects the BE's he/she ... Does the FE application has to have aliases already setup for the BE ...
    (microsoft.public.access.modulesdaovba)
  • Re: can i build a client data base
    ... database to track your own clients? ... Make a list of all the data you'll need to accomplish and what kind of data ... numbers, ID numbers, SSNs, etc but are not used for math should be defined as ... That's a very broad outline of the creation of a database by me, ...
    (microsoft.public.access.gettingstarted)
  • Re: Help with Paradox 9 table schema
    ... And it makes perfect sense in the Paradoxian ... to the invoice database and see how much money I made! ... the linkage of tables for lookups you do not need to use aliases. ... MyDocuments and shares - but you really need to be able to define shares ...
    (comp.databases.paradox)
  • Re: Selecting back end(s) to use
    ... individual mdb's and obtain organization-wide reports. ... I can send the reconnect ... > different database. ... >> What I would like to accomplish is that when user selects the BE's ...
    (microsoft.public.access.modulesdaovba)
  • Re: Help with Paradox 9 table schema
    ... Jim Hargan wrote: ... self-contained child databases -- so everything I use is always aliased, ... If you change the working directory to the child database, when you do the linkage of tables for lookups you do not need to use aliases. ... you can move the database from one system to another provided that you can map the location to the same letter on the new system as on the old. ...
    (comp.databases.paradox)