You have gotten some good advice already. I will add this.
It's not REALLY a "secret" but the secret of a "well-arranged Access database" is to spend time up-front in doing design and analysis work to determine requirements. That is: What do you have to work with (data source questions)? What do you expect from the database (report and display questions)? Given your other findings, how will you get from input to results (computation and processing questions)? How will you put all these things together (integration questions)? What do your application users need to know/understand and what will they see (interface questions)? If you do this right, you will swear you have just been brutally interrogated - by yourself. And yes, sometimes it can feel that way.
We can guide you but you need to ask narrowly targeted questions. Since we don't know your business or your local regulations, we will be good technical guides but poor business guides. Just remember, many of us are literally a continent away. You are in Dubai whereas I am in the southern part of the USA near the Gulf of Mexico. So we are unlikely to know your specific situation. Therefore, any questions you ask must be asked based on the assumption that we have no idea what you are doing.