Components
Home ] Access - Start Here ] Excel In Depth ] MS Office ] Visio Info ] Creating Web Pages ] Technical References ] Viruses ] Points of View ] Gadgets ] Just Links ] Monash ]

   Search this site or the web       powered by FreeFind
 
  Site search Web search

Participate in Ananda's Discussions
Post a message

Monitor page
for changes
    
   it's private  

by ChangeDetection

Up

Components of Access / VBA in More Detail

VBA is a glue language - it is the way you bind an Access object's event (e.g. the On Click event of a Command Button) to some action - like showing another Form, sending an Access Report to the printer or changing the data.

As I keep saying to my students, Access may appear as one program, but it is a combination toolkit. Therefore, to be conversant, a programmer needs to understand elements of:

Amidst all this, it is of actual and long term benefit to have some coding conventions in writing VBA code:

If Data Access is the Key...

MSDN: Data Access Resources is a compilation of links to articles about ODBC. There is also another compilation called MSDN: Microsoft Data Access Technical Articles Overview. A general compilation is MSDN:Access Resources. If you are moving on to SQL Server, there is an MSDN compilation of links here.

MSKB Q167179 discusses how to suck data via DAO into a VBA variant variable containing an array.

We see scattered references to the MS DataShape Provider or the OLEDB Shape Service.

Newcomers often believe that new version software will be better, faster etc... Well, Access 97 is slower than Access 2000 because of the new Jet 4.0. Q240434 tells you how to optimise Jet 4.

Ok, so that's the plumbing, but before you start...

If you have developed in dBase, Paradox/DOS, ANSI C, Pascal, COBOL, you should a little about Software Engineering before you embark on a feature laden software project.

Most database developers should be familiar with an ER Diagram - When All You Want is an ER Diagram. It's always better to start off well by having the design of the database take care of gross functions and features.

ER Diagrams are good for databases whose main objective is to store data and then to retrieve based on some criteria. However, if you are going to design a workflow system, where data is secondary and you are more interested in the context and meaning of the information then you should do some Use Case Modelling to document the request. Microsoft has on board, Terry Halpin, a real thinker on ORM

Traditional Programming Projects (Predictive Projects) define a waterfall or formal - design-develop-release-production phases. Current thinking emphasises Agile methodologies - more iterative and more responsive to the client changing their mind. See The XP Project in Start this XP thing.