Selecting back end(s) to use

  • Thread starter Thread starter Alp
  • Start date Start date
A

Alp

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
 
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.
 
Hi Doug,

Thank you for your response. The reson of having BE's of same structure is
that the application will be used by the HQ of an organization which will
use its individual branches' data. To keep the uniformity among these
branches as well the HQ, this method was selected, ie.e each branch uses the
same application. To ease HQ's operations, now I'm trying to provide them
with an application with which they can utilize the data provided via these
individual mdb's and obtain organization-wide reports.

The idea looked nice and warm... but now have to accomplish.

I am actually using another code "reconnect" for my normal reconnections and
was hoping to incorporate and/or modify it to accomodate this but somehow
became brain-dead. That is why I'm here for help. I can send the reconnect
code if you'd like to have a look.

Alp
 
Back
Top