A database of diversions

G

gramps

Hi
This is my first venture into Access so please bear with me.
I work in the London bus industry and what I want to do is to compile a
database of the standard diversion routes that are suitable in event of road
closures etc. The diversion details are stored in text files with a reference
number allocated to them and I would like to be able to be able have a
database such that I can enter a start and finish point and obtain a copy of
the appropriate route. I hope I have explained my requirements adequately and
many thanx for any help you can give.
 
A

Access101

Can I assume that you have Bus 1,2,3?

And that each bus along its route, has X number of diversion routes,
depending upon where it is in the course of it's travels?

And, is a diversion route currently linked to a Stopping point, or a street
corner?

I would think you'd have to have one table of buses, with a Many to Many
relationship to each stopping point. (because one bus can have many stopping
points, and one stopping point could have multiple bus routes going by it).

And then a table of diversion routes relating to the stopping points table,
with a one to many. Assuming that when Bus 1 arrives at that Stopping POint
it uses the same exact Diversion route as Bus 2 when it arrives at that
Stopping Point and needs to be diverted.

How are we doing?

If the Text file is frequently updated, they'll need to be a way to import
that file into the db on the fly, as well as match up the "updated" data, and
append the new data.
 
G

gramps

Thanx for the quick response. Taking each route individually there are X
number of well established diversions along the length of the route linked to
the road junction where the diversion starts. As you say there are some
diversions that have more than 1 route using it in whole or in part at any 1
time. A further complication could be the fact that the diversion could apply
in 1 or other direction at any one time or it could apply in both directions.

Although most of the diversion routes are well established it is sometimes
necessary to invent a new diversion on the hoof or we may win a contract to
operate a route previously run by a different operator and these would need
to be added to the db. I was originally thinking of having a separate table
for each route having fields for the start and finish points together with a
reference number which called the relevant text file which could then be
published as a notice for drivers to follow. In view of the overlap of routes
using a diversion this may well not be the best way to go, so any help on the
basic structure of the db and detailed advice you can give would be really
gratefully received.
 
Top