Hi Cetin

>You're welcome:)

Updates:
- When I ran multiple instances of the VSORM.EXE the C5 problem has been avoided from my app. I tried to run the empty report thrice and successfully exited the app. Did the same in an old copy of the app and it C5ed under similar situation.

- This empty report had a surprise find when it ran through VSORM.EXE. Though the RM report preview window shows grey (as usual) the message box stating that there is no data to display belonged to VSORM.EXE. The title bar of the messagebox contained the text "vsorm" so I presumed that the ActiveX has forced VFP to display the message.

- Memory file was the way to go.