Advise on Large Project

[GyverX]

I am hoping to get some direction on this issue.
In a nut shell… I am discouraged on what route to go- Access or some other DBM.

What I am doing is creating an in-house database for a Freight broker company that I work for. There are only 5 of us here. The company as been in business for over 20 years with a max employee count of 5. This is a family run business and has done all of there database in Excel, but that really puts it loosely in terms.

What we do now is create load confirmation to send to carriers for the loads we cover in an Excel sheet formatted and DESIGNED to look like a form. Then saved as a file for each one while certain edits for each one has been made depending on the circumstances of that load. Then we print that Excel sheet out and staple it to the order and put it on a board for 2 to 3 days ahead.
What I am trying to do is, make a database and app out of Access for all employees to use and make it super simple to use as well. The employees are not computer literate to say the most… With in this project I am wanting to separate the database into a SQL but I really do not want to use MS SQL Server. Just a standard SQL should work and I know how to set them up.
My problem lays in this… When I create a form, to represent the load confirmation that the employees are used to, it turns out to be to-many controls on that form.

I have Access 2010 at home and Access 2007 at work. I have been using my main resource for learning all this at Lynda.com, The internet and scouring various forums.

With something this big, Should I be looking pass Access and to something bigger?
We run about 30-to 40 loads a day. I want to stream line the process of this, make the integrity of the data that gets put into the confirmation solid, and be able to change something and have it change system wide.
I have attached an image of my Table Relationship to help give a better idea of what I am working on.

Thanks
Jason

 

[MexOkie]

The database I use is probably 10x more complicated than what you posted. For an office that small you have to weigh the costs of using something "bigger." Access' ease of use lends itself for these types of projects. The only thing, I belive, that can hamper your database is data size. I might be wrong but I believe Access limits you to a 2GB database.

As I mentioned, I use a very complicated data structure but we have the luxury of purging our data at will. We are not bound by long term data retention.

I wish I could offer you more advise but that is all I can point out to you (size). Good luck!

 

[GyverX]

The database I use is probably 10x more complicated than what you posted. For an office that small you have to weigh the costs of using something "bigger." Access' ease of use lends itself for these types of projects. The only thing, I belive, that can hamper your database is data size. I might be wrong but I believe Access limits you to a 2GB database.

As I mentioned, I use a very complicated data structure but we have the luxury of purging our data at will. We are not bound by long term data retention.

I wish I could offer you more advise but that is all I can point out to you (size). Good luck!

Ya The Size is an issue but I was planning on going to a SQL link once I have the bugs and process worked out. I can run the SQL here at the office and keep it in house, Was thinking of running it off of a Synology NAS using MariaDB. That should solve the size issue.