Barbara,

Thanks for the input (you too Gar).

I don't usually use the Wizard for my Database screens, however, this particular situation was time critical and I thought I could save some time (Hah!).
What I learned was that the parent app maintained certain files that were always open. My child screen did not utilize those files, however, the Wizstyle control included them in the workarea array, and upon return to the parent app, attempted to write a logging record to a control file who's, (don't ask me how) buffer properties were altered by my program. I don't pretend to understand what happened, but was able to write a workaround and the client will live happily ever after,

Again, thanks.



Barry,
>As Gar said, the WizStyle control code has some nasty bugs in it. Most of us have developed our own versions, whether through a third party framework or our own in-house development.
>
>However, in this case, you might try running the EXE from the command window (DO MyApp.EXE). This usually allows the debugger to come up when you need it. Then following through the code you can see where it went wrong.
>
>HTH
>Barbara
>
>>Hi Barabara,
>>
>>Thanks for responding.
>>
>>I believe the fact that the program runs properly from the project would probably suggest that the correct file was selected. I did, however, trace it to verify this.
>>
>>This program uses the Wizstyle.vcx (buttonset) control and appears to hang up in the updaterows event. I cannot issue a Set Step On in the .exe as it would give me the "Feature Not Available" error message. I don't know where to go from here. The program has always run properly and I made no changes that would have affected the buffering schema.
>>
>>Any other ideas?
>>
>>TIA
>>
>>Barry