First Set up of My database environment

There are a lot of advice available in the cloud to explain on how to use and how to program Microsoft Access database. Thus I am not prepare to revamp the cycle. In this blog, I am going to put our foot down to the ground and build the database and make it functional in reasonable timing.

The Microsoft Access that I am using is of 2010 version. It is going towards cloud operation and we should be able to created web database. But one of the drawback is its web database is not compatible with VBA coding. This post a limitation on "automation" requirement. Hence the database that I am going to build as an example is a desktop database. Intranet is common now in manufacturing plant. Thus I am going to build the database base on network operation. Nevertheless, during the initial start up, I will try to set everything based on a single desktop operation and when it comes to a functional stage, then I will guide you through the simple steps to make it functional in network environment.

To clear any doubt, I would like to clarify that I am not in any relation ship with Microsoft. I am also not very clear on the final unseen limitation that Microsoft Access posed. The only thing I can be sure is that I had been using the system and running the program I designed for years and face no difficulty to-date. Thus it should be alright for the way that I use the program. Just in case we do face any limitation if future, then we will work together to rectify it and progress.

During this initial start up stage, I am creating a new folder in the c:\ drive and naming it as c:\KCBDatabase. In this folder, I am creating a sub-folder and naming it as c:\KCBDatabase\Data.

After creating this two folders, I start the Microsoft Access 2010 and created two new blank database. The first blank database is created in the c:\KCBDatabase folder and named as KCBSystem. The second blank database is created in the c:\KCBDatabase\Data folder and named as KCBData.

So, I am planning to create all tables for keeping our raw data in the KCBData database and the KCBSystem database will be the front-end operational system that linked all the tables from KCBData. All other queries, forms, reports and modules will then be created in this KCBSystem as a frond-end operating system.

The next step that we are planning to do is then to create the first table, which will store some specific data of the organization.