An Overview of the Objects in Access (or "What goes Where") Each of the main objects in an Access database has a main purpose, and in order to be able to use the database effectively, you will need to use the object that is best suited for the task that you have in mind. Tables Queries Forms Reports Macros Modules Tables This is where the data is stored, and that should be it. The user shouldn't be entering data directly into the table, and it is usually better if the user never sees the tables themselves, especially if you are storing foreign keys in the table (i.e. instead of storing Jaguar, you are storing the value from the lookup table for Manufacturers, which might be 5). Top Queries These have two main uses. Firstly to perform actions on data, such as deleting data, or updating data, and secondly, as a basis for forms and reports. Queries are written using SQL (Structured Query Language), although in most cases you can build queries using the Query Grid. Top Forms This is the main part of the database that the user will see, certainly on screen. All data entry should be performed utilising a form, and also this should be where the user performs interacts with the data, through the use of command buttons or similar controls. Forms should not be used to provide printed copy though. Top Reports These are used to provide hard copy to the user. As such they may be thought of as a snapshot of the database at a certain point in time, and therefore it is often useful to ensure that there is a date and or a time on the report. Top Macros These should only be used to quickly develop applications, and certainly shouldn't be present in the finished version (with the possible exception of the AutoKeys macro group, which is useful for application-wide hot-keys). The reasons for this are many, but most importantly, macros can't handle errors, so if the code fails at any point (and it will do!!). Also, using a module gives your application greater flexibility, especially as it appears that macros are gradually being phased out of Access. Top Modules This is where you can get serious about the application development. You can create procedures that communicate with other Office applications, other applications, utilise the Internet, use standard and custom Windows controls, and add error handling to ensure that when things go wrong, there is some control as to what happens. Top   HOME | NEW | TABLES | QUERIES | FORMS | REPORTS | GENERAL | API | DOWNLOADS | TUTORIAL | RESOURCES E-MAIL Copyright & Disclaimer

Last modified at 06/06/2006 15:02:10