>Hi Tracy.
>
>>Anyone ever seen a problem exporting to Word only? All other exports work. MSFT Word 2007 is installed. It appears to work (no errors), but nothing gets written to a local directory where the file should go.
>>
>>Works every place else (other customers) fine and exporting to all other formats (XLS, PDF) work fine as well.
>
>Are you checking the return value of SetParams?
>
>Doug

Thanks for the help Doug. Yes we are checking the return value of SetParams, and it is 0 so it goes on to run processreport(). In processreport we display a wait window which shows that the report is processing. The wait window appears as it should. The problem has to be somewhere in processreport().

I was hoping maybe someone had run into this previously and would be able point me in some direction to check for example disabling script blocking in Norton AV, disabling hostile activity watch kernel in McAfee, etc which I've already done). I was hoping to avoid having to modify the xfrx program to trap for it unless absolutely necessary since that would involve a test exe to put into place and I hate to do that during the holiday season for a live 24/7 critical app (and I DO mean critical).

I just looked up online how to call initlog() to do a log and I may end up doing that with a test exe after the holidays if I cannot figure it out any other way.

It is only happening at this one client location but on all machines there and this code has been in place for years.