| Software development in Microsoft Access
| |
| | and qry prefixes on these two objects, it
|
| is relatively simple and almost anyone
| |
| | always ensures that the tables are shown
|
| can do it but if you want to be taken
| |
| | first and then the queries because t
|
| seriously by professional database
| |
| | comes before q.Other objects that need to
|
| developers then there are some mandatory
| |
| | be named include the bound and unbound
|
| rules that you must follow whilst
| |
| | controls found on forms and reports.
|
| developing your database. One of the
| |
| | When you create a form or report using
|
| first aspects professional developers
| |
| | the wizard or AutoForm or AutoReport each
|
| will look at when reviewing your work
| |
| | of the controls are named the same as the
|
| will be the naming standards you are
| |
| | field names. Now whilst this is by
|
| using for your Microsoft Access Objects.
| |
| | default, it is not really an acceptable
|
| Microsoft Access allows you to use, what
| |
| | way of naming controls. One of the key
|
| is considered in the professional
| |
| | reasons we don't want to do this is that
|
| database development world, poor naming
| |
| | sometimes when we are working with forms
|
| standards. For example in your field
| |
| | and reports we want to refer to the
|
| names, you can have spaces however in the
| |
| | control rather than the field. By having
|
| professional world that is a major no
| |
| | the field names the same as the object
|
| no.One of the reasons we don't use spaces
| |
| | names, you can often have a situation
|
| in Microsoft Access is that when you
| |
| | where the wrong control is referred to.
|
| start creating complex queries and
| |
| | The way we overcome this, is by naming
|
| functions that refer to fields, if you
| |
| | our controls based on the control type.
|
| have spaces in the field names it is
| |
| | For example if our field was called
|
| possible to put two spaces into the field
| |
| | fldPostcode and the control we are using
|
| name but it only appears that there one
| |
| | for this field is a text box, then we
|
| space. What this means is that your
| |
| | would name the text box txtPostcode.
|
| query won't work and can sometimes take
| |
| | Below is a list of prefixes for the forms
|
| many days to find the mistake. The key
| |
| | and report objects.frm - Forms
|
| issue is that you must never use spaces
| |
| | rpt - Reports
|
| in your field names, database names or
| |
| | lbl - Lables
|
| any of the seven different object types.
| |
| | txt - text boxes
|
| There are in fact two ways that you
| |
| | cmd - command buttons
|
| should be naming your fields, database
| |
| | lst - List Boxes
|
| names and so on.Naming FieldsLet us say
| |
| | cmb - combo boxes
|
| for instance you wanted to create a field
| |
| | opt - option buttons
|
| to store the Postcodes for the suburbs
| |
| | ole - ole objects
|
| your customers live in. We could write
| |
| | chd - Child Objects (Subforms or
|
| this field in two ways, the first thing
| |
| | subreports)For a full list of all prefix
|
| you must do for fields is to add the
| |
| | names that you should be using in
|
| prefix fld at the start of the field.
| |
| | Microsoft Access Development is shown
|
| Then add the field name as required
| |
| | below:Microsoft Access Objectsdb -
|
| -fldPostcode or fldPost_codeEither
| |
| | Database
|
| technique is quite acceptable. If you
| |
| | tbl - Tables
|
| were developing a field for Post Codes,
| |
| | qry - Queries
|
| that is codes on posts, then the
| |
| | frm - Forms
|
| recommended way for writing the field
| |
| | rpt - Reports
|
| name would be -fldPostCode or
| |
| | mcr - Macros
|
| fldPost_CodeYou will notice that in the
| |
| | mdl - ModulesTable Objects -tbl - Core
|
| second example the second word is in
| |
| | Data Store
|
| capitals rather than in lower case. The
| |
| | tmp - For temporary Tables
|
| use of capital letters signifies that
| |
| | bck - Tables that you have backed
|
| each word represents a separate aspect of
| |
| | upForms & Reports Objects -frm - Forms
|
| the field, so in this case the code in
| |
| | rpt - Reports
|
| capitals means you are referring to codes
| |
| | lbl - Lables
|
| on posts. The same naming principles
| |
| | txt - text boxes
|
| apply to database names, and each of the
| |
| | cmd - command buttons
|
| seven Microsoft Access object
| |
| | lst - List Boxes
|
| types.Naming TablesWhen naming tables,
| |
| | cmb - combo boxes
|
| there are three prefixes that you can
| |
| | opt - option buttons
|
| use. The first prefix tbl is used for
| |
| | ole - ole objects
|
| the core tables you will be storing your
| |
| | chd - Child Objects (Subforms or
|
| good data in. The tmp prefix is used for
| |
| | subreports)Report Names -rpt - For
|
| tables that will be storing temporary
| |
| | General Reports
|
| data. It is also recommended that you
| |
| | cht - For Chart Reports
|
| import your data into a temporary table
| |
| | lbl - For Label ReportsVariables -str -
|
| before inserting the data into your good
| |
| | strings
|
| data tables. We do this for two core
| |
| | ole - ole object types
|
| reasons; the first is that testing your
| |
| | int - integers
|
| data in a temporary table is much easier
| |
| | dec - decimal
|
| than doing it on the fly while you are
| |
| | dte - datesModule Objects -sub -
|
| trying to import your data.The third
| |
| | Subroutines
|
| table prefix I recommend being used is
| |
| | fn - Private Functions
|
| bck for backup tables. The key advantage
| |
| | pfn - Public FunctionsUsing the naming
|
| of using these prefix's on your tables is
| |
| | standards shown above will assure that if
|
| that Microsoft Access will automatically
| |
| | you do require assistance from a
|
| group them by the prefix, which means you
| |
| | professional database developer that they
|
| will keep all your good tables together,
| |
| | will take you far more seriously than
|
| your temporary tables together and your
| |
| | before because you have shown a
|
| backup tables together.Naming the Seven
| |
| | professional understanding on how to name
|
| Access Object TypesWhen you are working
| |
| | your database object. This will certainly
|
| with the seven different object types
| |
| | give you credibility in the eyes of
|
| that make up Microsoft Access, each of
| |
| | professional database developers.Chris Le
|
| the objects has its own prefixes. A list
| |
| | Roy is a professional software developer
|
| of those prefix names you should be using
| |
| | and has been developing software
|
| for the Access Object Types are shown
| |
| | applications for over 20 years in Visual
|
| below -db - Databasetbl - Tablesqry -
| |
| | Basic, VB .net, VBA, C++, Microsoft SQL
|
| Queriesfrm - Formsrpt - Reportsmcr -
| |
| | Server, Transact SQL, ASP, PHP and
|
| Macrosmdl - ModulesOne of the key reasons
| |
| | Microsoft Access. He is the Managing
|
| we name our tables and queries with a
| |
| | Director of One-on-One Personal Computer
|
| prefix is that when you are working with
| |
| | Training that trains over 2000 people per
|
| these two object types in the query
| |
| | year across Australia and Overseas from
|
| window, Microsoft Access simply lists all
| |
| | basic Microsoft Office functionality to
|
| tables and queries together without
| |
| | advanced Database Design and VBA.
|
| differentiating them. By using the tbl
| |
| |
|
