Hmmm... How many times it's used is up to the user... I guess I'll create it at init, then it's always there if needed.

Thanks,

-Michelle


>Oh, that's your call; typically, if a form is used often, I will create it at init time, and display and hide as needed, for speed. If it's only needed once or twice, if at all, I just create and destroy.
>Mark
>
>>There's not much to the form, so that would work. When I want to call it, do I create it then? Or do I create it when the class instantiates?
>>
>>Thanks,
>>
>>-Michelle
>>
>>
>>>You could always define a form class in code and create it on the fly, which is no problem unless the lookup form is complex.
>>>Mark
>>>
>>>>If your making a class, and one of the buttons in the class calls up a look-up form, is there some way of bundling the form in? I know I could just include the form in the zip file with the class, but I'm wondering if there's some way of making it all self contained? Same for bitmaps, too. I've got pictures on a couple of the buttons.
>>>>
>>>>Thanks,
>>>>
>>>>-Michelle