Renoir,

Pardon me for jumping in, but I have tried the coverage profiler and discovered as well that the result was extremely complex. Therefore, I settled on two strategies.

First, of course, is to start with a very simple example. Throw up a page with a pageframe and a command button on one page. Click the command button, and check the coverage profiler. A smaller problem is always easier to tackle.

From doing that I came to an unorthodox approach: Reduce or eliminate code in "automatic" events. Maybe I'm dumb, but I just could not handle the complexity; I much prefer a simplified solution. For instance, if an object contains INIT code, it may fail. You now have to check for that and handle it. I found it much easier to keep INIT empty and always let an object load, then determine if it could do its job. It can also get very sticky when you've got When, Valid, OnFocus, LostFocus, and so forth on controls. The events there tend to fire back and forth. Maybe I'm dumb, but I could never quite untangle it, so the controls have no valids; when the user saves the form the entire form is validated, and a list of all problems is displayed. Users seem to like it better and it is MUCH easier to code.

Just my $.02


>Where can I find information on what events are automatically fire by other events? For example, are page Activates triggered by the Refresh of a pagefram? That's not my question, just an example of what I'm looking for. Seems like I saw it somewhere, but can't locate it now. Thanks!
>
>Regards, Renoir