Question Choose which BE to open

[josephbupe]

I would like some detailed info, if possible with a sample mdb, showing a Front-end that prompts user to select a back-end through a form listing all BEs stored on local machine.

Thank you in advance.

 

[DCrake]

Is this the kind of thing you are looking for.

Sample.

Not exactly as per your question but it shows how to be selective in which back end is linked to the front end at point of login.

David

 

[josephbupe]

Thanx xcraft.

It's in that direction. But how can i make it prompt for location of the BE file when i login, so that if i have more than one BEs i would just choose one of them to load?

My users are'nt connected and they will be bringing in copies of their BEs which i will put in one dir on local machine at the main office (HQ). I want to be using these BEs (North_BE.mdb, South_BE.mdb etc) for searching status of different individuals as reported from different locations (users). Users will be sharing the BEs among themselves, too, for their own use at their locations.

I'll appreciate.

 

[namliam]

Have a search for "File Pick" or look into the "Dir" command to find any BE's and load them into the DB/Combo to be selectable.

Good luck !

 

[Rabbie]

I would like some detailed info, if possible with a sample mdb, showing a Front-end that prompts user to select a back-end through a form listing all BEs stored on local machine.

Thank you in advance.

The usual configuration is to have front end DB stored on each local machine with the BE stored on a central cserver/computer.

 

[DCrake]

Before I give you the solution, here are a few things to take into consideration before embarking on this route.

1. Can each location only open there own mdb?
2. If you knew the location would you know the name of the mdb?
3. Can a location open more than one mdb?
4. Are the structural contents of each mdb identical?
5. Why is all the dat anot in the same mdb?
6. How do go on analysing across locations?
7. Does each location have read/write/delete functionality?
1.
If there is a political reason why each location has there own mdb. (They are not allowed to see each others data) then how can you prevent them from opening a different mdb?

2.
If a user logs in they could have a code attached to them that signifies which data they have access to and which mdb contains the data. This way you can autiomate the linking of the correct mdb.

3.
If a manager from location A is at location B and wants to look at his data can your system provide that caperbility.

4.
I am assuming that each mdb is identical it's only the contents that are different. You system would fall over if tables were missing from one mdb or more tables are added to a certain mdb.

5.
If you had an extra field in your data table that identified the location then when the user opens the database only those records which they have access to will be made available.

6.
If you data is in seperate mdb's at some point you are going to have to amalgamate them to analyse the whole organsiation's data. Conversely you will need to split the main mdb prior to segregation.

7.
If each location can add/edit/delete you may have grate difficulty in mainitainong referential intgerity and uniqueness amongst primary and foreign keys.

There are further issues to explore but consider the above first.

David

 

[josephbupe]

Hi DCrake,
1. Can each location only open there own mdb?
A. Not, not only their own mdb if they will be able to choose from
the available mdbs they might have gotten from other locations and
stored locally on their machines.

2. If you knew the location would you know the name of the mdb?
A. Absolutely! Mdbs (BEs) for each location will be named after the
name of location: Southern_BE, Nothern_BE, Eastern_BE etc.

3. Can a location open more than one mdb?
A. Yes, but only one at a time. The user may choose from a list of
available mdbs (BEs).

4. Are the structural contents of each mdb identical?
A. Yes. Table structures of all mdb from different locations are
identical.

5. Why is all the dat anot in the same mdb?
A. Different locations have their own data in one mdb because
currently no physical network exists for among them.

6. How do go on analysing across locations?
A. Hopefully, that will be delt with later.

7. Does each location have read/write/delete functionality?
A. Yes, depends on user access level.

8. If there is a political reason why each location has there own mdb.
(They are not allowed to see each others data) then how can you
prevent them from opening a different mdb? A. Lack of network link.

2. If a user logs in they could have a code attached to them that signifies
which data they have access to and which mdb contains the data. This
way you can autiomate the linking of the correct mdb.

3. If a manager from location A is at location B and wants to look at
his data can your system provide that caperbility.

A. Yes, at the moment, only if they shared the same mdb.

4. I am assuming that each mdb is identical it's only the contents that are
different. You system would fall over if tables were missing from one
mdb or more tables are added to a certain mdb.

A. Yes, you assuemed well. tables are identical in structure, only the
data is different.

5. If you had an extra field in your data table that identified the location
then when the user opens the database only those records which they
have access to will be made available.

6. If you data is in seperate mdb's at some point you are going to have to
amalgamate them to analyse the whole organsiation's data. Conversely
you will need to split the main mdb prior to segregation.

7. If each location can add/edit/delete you may have grate difficulty in
mainitainong referential intgerity and uniqueness amongst primary and
foreign keys.

I hope to hear from you soonest.

Thanx.

 

[gemma-the-husky]

the trouble with showing all back ends is .... search for .mdb on your computer and see how many databases you have.

now a halfway house that might work for you, is to store a folder name in your app, and then do a dir loop to find all the .mdb s IN that folder - then present these to the user.

if you are using multiple folders, then its far harder.

but then you also need a way of deleting all your linked tables, and relinking the newly selected ones, and ensuring they have linked correctly. Taken altogether, this isnt really a trivial exercise at all.