If you'd like to create a "complete" web application, then things can get a lot more complex/complicated even for a simple task.
Web apps are server-client based, meaning that you'll first need to request the letters from the server, then send the new order back, all these with HTTP(S) requests.
Unfortunately the access database isn't a proper HTTP(S) server, just a database. Meaning you won't be able to directly request data from it. It might function as a HTTP server, but even then it would be a very bad practice to let the client interact with it directly for security reasons.
I shamelessly stolen a picture to illustrate the idea:
Picture[
^]
So you have the client that you as a person can interact with, and have a database server running (access). You're only missing the server that interacts with both the client and the database.
There are a lot of HTTP servers to choose from, the most popular ones are Apache and Nginx (I prefer the latter). Just pick one that has easier installation and more documentation available.
The server itself won't do much by itself after installing, just serve files that you request from it with the client.
So you'll somehow have to tell it what to do with a request, meaning you'll have to implement the logic of interacting with both the database and the client, and you can do this with the help of server-side(backend) programming languages.
There are a lot of options here as well (NodeJS, Ruby, Go etc.), but for starters I'd recommend PHP, as it can be put in your html(now php) file.
I won't go in detail on how to write your PHP code, as I don't have a lot of experience with the language, but I'm sure there are a lot of tutorials and guides online (you actually don't need books for a lot of stuff).
There will be two scenarios on the server you have to implement:
-Upon one request(GET), it will get data from the database with SQL, and send it to the client.
-And on another request(POST), it will update the data in the database with the one that was sent by the client.
(As far as I know access uses SQL as well)
As for the client:
Start thinking in divs, everything is a div.
(This really is a generalization, and I can see the cringe of the webdevs reading it, but it will make your life easier.)
So the containers are divs, and the boxes are also divs, but smaller. There you have your boxes, just draw them like you would draw the containers, just give them different CSS class and rules.
Apart from creating the content, you will need to somehow interact with them, this can be done with javaScript. I'd suggest going through javaScript guides and tutorials to get the hang of it. You can also just simply use jQuery first, as it is easier to use compared to vanilla javaScript, however it would still be essential to learn how JS works exactly later on.
Another concept to look into is AJAX requests, you'll probably need it for your submit button, with it you can send the data to your server.
There will be a quite lot of reading and learning involved, but writing a full web application is like writing 2 applications that interact with eachother, so it will be twice the work.
I won't go much more into detail, as this answer is already an essay, and should be enough to get you started.
I hope I could help.
Submit an article or tip