fat controller
Slightly round the bend..
- Local time
- Today, 11:22
- Joined
- Apr 14, 2011
- Messages
- 758
Before I begin, I will openly admit that my knowledge of Access is pretty limited, and that I am learning as I go.
I have built a few databases, although each has been a development of the the one before it so more developing, refining and expanding what I have done before; the latest version is proving to be highly successful now that it is in operation - I should say that it is fairly simple (I would imagine that most of the experts on here would build it standing on their head), in that it has a form which users simply enter information into the relevant fields which populates the table, and then reports can be taken within given parameters (main one being date from and to).
However that success has led to me being presented with new challenges, as more and more people are seeing the benefit of being able to get access to the information they want quite easily.
The latest one has me totally lost, hence me turning to you all for help, simply because it involves moving or displaying information in different locations.
In short, I have a fleet of vehicles (up to 150), and each vehicle is fitted with four items of equipment; each item of equipment has a serial number. I need to be able to track those items of equipment coming into stock from the supplier, then onto each individual vehicle, as well as being able to go back into stock and even back to the supplier.
There is only one supplier, and each vehicle has a unique ID number. The four items of equipment are entirely separate to each other, and it is common for only one of them to be changed out at any point in time.
I need the database to be able to show:
- what four items are on which vehicle at the time of the report, be that an individual vehicle report or a full fleet listing;
- what items are in stock
- the history of an item (which vehicles it has been on, and if it has been in and out to and from the supplier a number of times)
This may sound really silly to most on here, but I cannot even work out how many tables I need for this - and I would openly admit that relationships has me baffled.
Any, and all help gratefully received
I have built a few databases, although each has been a development of the the one before it so more developing, refining and expanding what I have done before; the latest version is proving to be highly successful now that it is in operation - I should say that it is fairly simple (I would imagine that most of the experts on here would build it standing on their head), in that it has a form which users simply enter information into the relevant fields which populates the table, and then reports can be taken within given parameters (main one being date from and to).
However that success has led to me being presented with new challenges, as more and more people are seeing the benefit of being able to get access to the information they want quite easily.
The latest one has me totally lost, hence me turning to you all for help, simply because it involves moving or displaying information in different locations.
In short, I have a fleet of vehicles (up to 150), and each vehicle is fitted with four items of equipment; each item of equipment has a serial number. I need to be able to track those items of equipment coming into stock from the supplier, then onto each individual vehicle, as well as being able to go back into stock and even back to the supplier.
There is only one supplier, and each vehicle has a unique ID number. The four items of equipment are entirely separate to each other, and it is common for only one of them to be changed out at any point in time.
I need the database to be able to show:
- what four items are on which vehicle at the time of the report, be that an individual vehicle report or a full fleet listing;
- what items are in stock
- the history of an item (which vehicles it has been on, and if it has been in and out to and from the supplier a number of times)
This may sound really silly to most on here, but I cannot even work out how many tables I need for this - and I would openly admit that relationships has me baffled.
Any, and all help gratefully received