thanks Evan - I may have narrowed the report issue down to leaving the report designer open when running it

the BeaUtify issue is not really enough to go to any great lengths on ...

thanks! Ken

>Ken, if you can isolate these two errors to a tiny bit of code, you can email me and I will see if I can reproduce them. Can you get:
>- beautify to crash on a small code snippet (10 lines)?
>- can you reduce the report to just 1 table with a few records and only one field on it?
>
>If you can, send it to me at edelay@vanhosp.bc.ca
>
>>Since upgrading to 6.0 SP3, I am encountering two intermittent and minor but irritating problems that I didn't (and still don't) have in 5.0a.
>>
>>1) The "Beatify" function will often give me an "API call caused an exception" error message. It doesn't seem to hurt anything, and will almost always work if I try it again immediately. It happens about 10-20 persent of the time I try it and almost always the first time of the day.
>>
>>2) In report preview, I get the deadly "fatal exception" and get kicked out, about 5-10% of the time when I use the controls to go to the next page. I can always pop back in and run the report and go to pages just fine. (This happoens from command window - untested in any exe)
>>
>>Has any one else had these problems and/or have a solution?
>>
>>thanks!
>>Ken