Bryan,

>Is there a difference between VFP Codebook and VFP Codebook for Mere Mortals? If so, what are the differences?

Yes there are. VFP3 Codebook is the original framework/book that was written by Y. Alan Griver of Flash Creative Management. We have taken the original VFP3 Codebook (with permission from Flash), debugged, enhanced and documented the original classes and added many new form and control classes.

Here are some examples of the enhancements we have made:

* Documentation - We have worked hard to create the best documentation possible. We have a companion Developer's Guide that covers the application development process step-by-step. As we answer tech support questions, we put the answers in the Developer's Guide for the benefit of other developers.

* Internal Documentation - We have added extensive internal documentation to the class methods that allow you to understand quickly exactly what a method is doing.

* Error Log / Reporting Class. This class logs all application errors - including the program calling chain and the computer environment. We have also added error checking that traps developer errors when running an application in Debug mode. For example, if a Developer enters an invalid ControlSource, we display the error in a WAIT WINDOW and allow the form to continue instantiating. Without this error trapping in place, VFP usually crashes.

* The Business Object classes in the Mere Mortals framework break through the limitations inherent with the original VFP3 Codebook classes. Parent and child business objects can reside on different pages of a pageframe. A single business object can act as both a parent and a child at the same time. Our business object classes can even handle extended family relationships such as grandchildren.

* Event Objects -The Event class allows you to create objects out of your application events. For example, if you are creating a Point-of-Sale application, you can create a Sale event that involves a customer, an invoice, invoice items and so on. Rather than hiding the functionality of an event in the Click event of a command button, you can specify the interaction of objects with an event class.

* User Access/Permissions - You can define three different types of user access for your applications:

1. Full Access
2. No Access
3. Read-Only Access

You can specify these different access levels for a form, or all the way down to a specific control on a form. If a user does not have access to a particular form, any associated menu bars or toolbars buttons are dynamically removed for that user.

* Developer Hooks - We have placed many developer hooks to the framework classes so that you can add application-specific functionality before and after critical framework processes.

* Tech Support - We offer 30 days free support that starts the day you ask your first question. We provide same-day response to questions you ask via e-mail. We have helped many developers get up and running quickly by means of our Developer's Guide and Tech Support.

And much more...If you have any specific questions please let me know. If you do not already own the original VFP3 Codebook you can also purchase it directly through us. Also, you can check out our web site at the url listed below.

Regards,
Kevin McNeish
Oak Leaf Enterprises Solution Design, Inc.
804-979-2417
www.oakleafsd.com