vigoferrell820
  How Can Cable Access Stations Promote Themselves Via Email Marketing?
 
I have no count of the number of times I've turned up for a client's site to execute either an audit of an Access database or had to repair or redevelop portions of a database only to find myself hunting around wasting valuable time looking for associated toys, dependencies and other related controls each time a simple policy of adopting some sort of naming rules and thus standardise an Access database would have been just the ticket; a ticket that can have said " Price cut " on my invoice to the client!

Identifying objects with Microsoft Entry databases (i. i. Tables, Queries, Forms, Reports, Macros and Modules) which has a derived set of events and prefixes makes people, developers and other members who will inherit an Access database lives more bearable together with manageable for future repair.

Microsoft Access fails to impose any disciplines and life develop into chaotic unless users make the extra effort right from the really start. So, the following conventions will elevate avoiding problems.

Putting aside VBA programming for now and just focusing in the objects readily accessible within a Access database, there are two sections I have to highlight in this article in the meantime to get you started:


  1. Naming conventions for a objects in your database

  2. Naming conventions for extended objects inside your database



Objects in Access

These prefixes can be used on the main six Access objects:


  1. tbl = Table

  2. qry = Query

  3. frm = Mode

  4. rpt = Account

  5. mcr = Macro

  6. mod = Component



When saving an alternative object in your Entry database, use the above prefix (with lowercase) and optionally add an underscore character (_) for a separator if required before specifying the name in the object.

For example, a table (checklist) of employees might are similar to tbl_Employees and also tblEmployees . Notice how I've capitalised the main letter (and for any word if a few word is used) as well as making it plural as this is the collection of individuals.

Additionally note, though Access is not really fussy, I tend not to own spaces at all between words or any place in the naming of objects generally - its good practice usually and more of the 'old school' approach particularly when programming Access using VBA.

Longer Objects in Access

The first section covered the essentials and once mastered users can take into consideration extending Microsoft Access object a little further and be even more explicit in adding a variety of use for an object.

For case, Access Forms are screen interfaces that end-users will interact with but the types of uses to get a form will vary with main input or read only form for a dialog box (pop-up) and then a message box.

To aid expand on this, these list maybe extended to help identify and group different types of use for various Access objects:


  1. frm = main form

  2. fdlg = dialog form

  3. fmsg = message form

  4. fsub = subform

  5. fmnu = selection form

  6. How about the other main objects? Well, here's some more:

  7. tbl = main table

  8. txls = Surpass table link

  9. todb = ODBC bench link

  10. ttxt = Text file link

  11. tsql = SQL bench link

  12. qry = principal query

  13. qapp = append query

  14. qupd = bring up to date query

  15. qmak = get table query

  16. qdel = delete query

  17. qxtb = corner tab query

  18. rpt = principal report

  19. rsub = below report

  20. mod = principal module

  21. edmonton excel programming, edmonton access programming
 
  Today, there have been 1 visitors (1 hits) on this page!  
 
This website was created for free with Own-Free-Website.com. Would you also like to have your own website?
Sign up for free