Company:	Abbott's Computer Services

Contact:	Jim or Phillip Abbott			(technical matters)
		Abbott's Computer Services		(see market for sales)
		7070 W 43rd, #100
		Houston, TX 77092-4444

		713/460-2844		fax: 713/460-1413

Email:		abbott@phoenix.net
		abbott@bztech.com		(email at marketing agent's)

Marketing:	James Barry
		BZ Technologies			jbdiver@bztech.com
		1-888-819-TECH			713/460-5333

Software:	This software is a MS Access documentation CASE tool that we have developed to assist the Access programmer in writing and defining the purpose and function of MS Access application tables and forms using the actual source code to create and guide the programmer or technical writer in this technical writing..

Purpose:	Research, build accessing table(s), and allow manual update to the discovered application research information already embedded in source tables and forms.

Overview:	This software processing in several phases. These phases are:

1. research the application tables and develop background information on each field in a table. (see h2Help table)
2. research the forms and develop a background on each bound and unbound control found on the form (see h4 and h5 tables)
3. Using the research from steps 1 and 2 create a data field and control look up table(s) with each entry being assigned a Help Id Number (see h2 and h6 table).
4. Assign a unique Help Id Number to each form control object.
5. Upgrade each control in forms to reference data source field so that the F1 key, What's This? prompt will use the MS Help File look up.
6. Several Query processors that will export research into XLS input for MS Word to help process and develop this into ODE Tools Help processor input.
7. MS Word help word processing and footnotes processor then exports its document into an MS Help File image(s).
8. CodeIdHelp (VBA) logic will update all forms so that they  reference the developed Help File as named by application developer. 
9. Help File master Topic and Map Word documents are included with source MDB when purchases along with directions on how to run these steps..

After all research tables are built, process uses a  VBA Function called CodeHelpId. CodeHelpId locates each data field, bound and unbound, each form control, and then add or update each with the its assigned Help Id Number.

In addition, the CodeHelpId VBA logic will, upon approval, generate VBA coding so that the h2Help table documentation features can become interactive in the application. It uses the INSERT into CBF module for this function.

Help On Cue VBA coding is also provided to remove the generated interface code using a function called HelpRemoveCode.

To interface to the collected research information, the generated VBA coding merged into each form uses the Enter and Exit event on text, combo, list, etc boxes (controls). It used the GotFocus and LostFocus events on command buttons. VBA coding is also generated for the Form_Unload event. Thus, if you use the on Enter or on Exit event care should be taken that no sub procedure naming conflicts occur. If so these event conflicts will have to be resolved manually or the generated coding removed.

Once you have all the application research is done, and the interface VBA coding generated (optional INSERT) you can begin keying your own field, commands, etc, help documentation into a memo box associated with each field and control. The research logic will not save command buttons with the prefix "Command" named references.

A small Help On Cue memo box can be activated on each form. The CodeHelpId logic generates VBA coding for a command button names cmbHelpOnCue. Use a question mark (?) on this command button. You must put this button on any form you want to the Help On Cue documentation and post development help activated on in a runtime environment.

If you do not want to have each of your forms interface with Help On Cue you can use the Form Look up and Loader included as part of the h2HelpController form. This combo box control allows you to select what form you want loaded, loads the form, and activates the Help On Cue interface for documentation data entry keying and using the memo text box provided..

When you are using the Form Loader to view forms (and to key help memos) you must comply with the number of active cursor rules for MS Access. This active cursor limitation is up to three (3). Since the form loader does not know what parameters are passed between forms embedded calls, this can cause weird and/or access level program abterms to occur.

For example, if you requested a form to be loaded by the Form Loader, and the form has a Tab Control you will see the Help on Cue memo entry box, but it can not be activated (keyed) because of the 3-active cursor rule. Or, if your form has more than two sub-forms you will see but can not key into the Help Memo box.

Because of the unique nature of this documentation coding you should make sure you do a source back up before you use it. There has been no known cases of coding was lost, but when using logic to add generated VBA coding into a CBF module, procedure naming violations may occur. 

Unpredictable results can and do occur. For applications that have a lot of VBA support coding its possible to accidentally run into sub procedure naming conflicts. 

For example, if you are already using the GotFocus event on a command button and the CodeHelpId generates a second GotFocus for the command button you will have two sub procedures with GotFocus events for this so named command button.

Once you've written all the field and control documentation for the application you can use the Function, HelpRemoveCode, provided. This coding will look at each form's CBF (code behind form) and remove all the CodeHelpId VBA lines inserted. This is done using the @ABBOTT comment suffixes to each VBA line so don't remove this if you're working in the CBF.

You can also elect to leave the Help On Cue VBA coding in the application. This will allow your application users to develop any unique training or in house conventions they may have related to data fields or form controls.

Restrictions and Notices

The application complies with all restrictions currently known to Access 95 and up. You must have MS Access in these versions in order to use this software. This CASE tool was developed with MS Office SR-2 installed. 

This software is the property of Abbott's Computer Services and is sold in the source form so that the application programmer can get full use of the product. Abbott's cannot be held responsible for any improper use of the software. Care must always be taken with any process that can add coding to any existing application.

This application software is restricted to one operator-programming platform. Any additional use or concurrent use by more then one programmer constitutes additional use and a multi-use license must be obtained. Currently this license is free and is needed for statistical purposes only. Please cooperate in this multi-use matter. This additional use license can be obtained by using my market email address.

Abbott's requires that the actual coding techniques and methods used in developing the research and code generating be kept confidential and not released or sold in source form to any second parties. Vendor arrangement can be made if you wish to include this body of work in source form as part of your application. Abbott's copyright and notices may not be removed when this work if included as part of a EXE or MDE application.

There is no restrictions related to distribution of Help On Cue when included as part of an MDE or EXE application. Help On Cue coding may not be included as part of, or any part of, any MDA or MDB application without licenses obtained from Abbott's.

User and/or purchaser is hereby informed that this Help On Cue body of work is a part of other work in progress by Abbott's. And that the purchase of this portion of logic does not imply the purchase of any concluding or final works as they related to any further refinement to this documentation research and generating function or special access or VBA coding.

Any publication contemplated, or that has already been published describing this product, a copy of this published works would be appreciated by Abbott's. Abbott's understand that this product could be released as an MDA but has elected not to do so at this time. Abbott's does not authorize any MDB, MDA, MDE, OCX or DLL release of this product unless license(s) have been obtained.

The Help On Cue source code is herein provided so that the MS Access programmer, both novice and advanced, can better understand how to write their own interface VBA to tables and forms, and how MS will permit on certain forms of containers, and how the Code Behind Form (CBF) can be obtained, displayed, and or updated on demand. 

Comments and other description code is provided where the actual purpose or intent of VBA code or series of VBA codes usage is not immediately apparent.

Should the licensed user of this product wish to comment, reflect on under designed features, point to better designs, or need consulting help please call, fax, or email Abbott's. There is no charge for reasonable assistant requests.
