I just re-read your initial post, and if you're not used to designing web pages or working with object-oriented programming languages because you're used to being a DBA, you might be struggling just to understand how the basics operate. Web pages are what is known as "state-less". It means that they generally do not hold on to ANY information that isn't kept in a "control" that is part of the web page... Thus gone is the concept of creating a variable and then being able to use the value of that variable to do things with, that so many of us got used to by learning the BASIC language, or FORTRAN, or even COBOL. VBA, which you can use within MS Access, now provides all the object-oriented abilities, but once the code that you attach to a given event for a given control runs, any values it was using are gone unless they are preserved within the control. It's a serious paradigm-shift. Only the controls retain any information. Your program code is largely there to implement what the user wants done when they click on something. Similarly, MS Access forms operate on the same concept. There is no "master program"... just code to operate when an "event" occurs. Data is kept in tables or in the various controls you design into a "form". That doesn't mean that you can't write your own functions or subroutines that code associated with a given form or control can call or execute. Recent versions of MS Access can have a form set up to use tabs, which is a convenient way to re-use space. Think of it as similar to opening multiple tabs in a browser. Each tab could display different elements, and in your case, possibly specific events or types of events that are associated with a given VisitID. Does that help?