Hi everybody.
I've been working with a database in Access 2003 which I wrote a couple of years ago, but it is now starting to show it's weaknesses and needs a vast overhaul.
It's purposes are:
Keep stock of equipment in the AVA department.
Record loans of equipment to staff and students.
Track when items are broken or need servicing.
Notify us when items are overdue for return.
Currently, if somebody wants to borrow a laptop, projector and six cameras, I have to input the data for each item seperatly, this takes a while, putting the start/end date and times, location, person borrowing the item etc. for each item.
Also, I need a way to stop my partner who's not very computer literate from accidentally deleting or overwriting users in the database, which she's done many times now.
Another problem with the current database is that there is no checking for duplicated or clashing entries.
I just noticed too that in the relationships for my old database, I didn't have any of the referential integrity things selected either!
I've decided I need to start it again from scratch since there are so many things that need changing with it.
I have found some code on this site to sort out the clashing bookings issue, which I am hoping to get working with the new system, and I found a post referring to an AV booking system from 2005, but I didn't really understand what they were telling the original poster to do.
Can anybody give me any pointers as to how to go about making the new version better, easier to use and do what we need it to do?
The new version needs to...
Check for duplicate entries.
Allow accurate stock taking of equipment.
Check for clashing bookings. - I have this working I think.
Allow me to book out multiple items per booking.
Preferably allow me to select items availble to book from a list that gets updated when items become (un)available.
Alert us when items are overdue. - I have to do this manually at the moment.
We are also implimenting barcode scanning for our equipment and staff badges so would need this working too, but they're just like normal keyboard entries really so it shouldn't be difficult.
I've attached an image of my current tables and relationships.
The TblEquipment... with just BookingID and EquipmentID is my attempt at making a list of items per booking, but I don't think it will work the way I was thinking. Also, I'm not sure if the TblRooms table would be needed or not, I just put it in to reduce the amount of typing I'd have to do for putting room numbers and names in different tables.
Sorry for the long first post, but hopefully somebody will be able to point me in the right direction
I've been working with a database in Access 2003 which I wrote a couple of years ago, but it is now starting to show it's weaknesses and needs a vast overhaul.
It's purposes are:
Keep stock of equipment in the AVA department.
Record loans of equipment to staff and students.
Track when items are broken or need servicing.
Notify us when items are overdue for return.
Currently, if somebody wants to borrow a laptop, projector and six cameras, I have to input the data for each item seperatly, this takes a while, putting the start/end date and times, location, person borrowing the item etc. for each item.
Also, I need a way to stop my partner who's not very computer literate from accidentally deleting or overwriting users in the database, which she's done many times now.
Another problem with the current database is that there is no checking for duplicated or clashing entries.
I just noticed too that in the relationships for my old database, I didn't have any of the referential integrity things selected either!
I've decided I need to start it again from scratch since there are so many things that need changing with it.
I have found some code on this site to sort out the clashing bookings issue, which I am hoping to get working with the new system, and I found a post referring to an AV booking system from 2005, but I didn't really understand what they were telling the original poster to do.
Can anybody give me any pointers as to how to go about making the new version better, easier to use and do what we need it to do?
The new version needs to...
Check for duplicate entries.
Allow accurate stock taking of equipment.
Check for clashing bookings. - I have this working I think.
Allow me to book out multiple items per booking.
Preferably allow me to select items availble to book from a list that gets updated when items become (un)available.
Alert us when items are overdue. - I have to do this manually at the moment.
We are also implimenting barcode scanning for our equipment and staff badges so would need this working too, but they're just like normal keyboard entries really so it shouldn't be difficult.
I've attached an image of my current tables and relationships.
The TblEquipment... with just BookingID and EquipmentID is my attempt at making a list of items per booking, but I don't think it will work the way I was thinking. Also, I'm not sure if the TblRooms table would be needed or not, I just put it in to reduce the amount of typing I'd have to do for putting room numbers and names in different tables.
Sorry for the long first post, but hopefully somebody will be able to point me in the right direction
