> As soon as this statement is executed, this is what I see happening in the debugger:
>
>1. It goes in and initializes some objects on form (3d boxes, mm_line)
>2. Sets the forms environment based on system settings (talk on or off, etc)
>3. Inits the SearchListObj on the find form
>4. Creates the data environment for the find form
>5. Sets up my data environment for the find form (collectionfindform)
>6. Sets up the grid on the find form
>7. Sets up and register the BizObjs on the find form
>8. Sets up the buttons at the bottom of the find form (Select, Find Now, Etc)
>9. Sets up the remaining controls on the form (checkbox, labels, etc)
>10. Sets up the controls I added at the top of the form for searching purposes

Problem is here somewhere...

>11. Destroys SearchListObj ??
>12. Destroys my CollectionFindEnvironment data environment ??
>13. Unloads my find form ??
>
>OK, now I'm really confused.

Somehow the form's INIT() is returning false which keeps it from showing. Look at the last control that gets setup before SearchListObj.Destroy() is called and look at the call stack window in the debugger to figure out what is calling or triggering the first destroy(). Likely culprits - bad controlsource, bad init/show/activate code added, cant find the class a control is based on, or some other flakiness.