>>>>>REPORT FORM (XRPTNAM) TO FILE (SUBSTR(STRTRAN(cpFilNam,'.'),1,8)+".RPT") ASCII
>>>>
>>>>Reports show that stupid little printing dialog, which unfortunatley makes it
>>>>impossible to use REPORTs in a COM DLL. You can however run reports in EXE
>>>>servers if you disable the UI function...
>>>
>>>Just out of curiosity, would it then be possible to REPORT FORM ... TO FILE, then print the file, or does the UI pop up any way? I've never noticed.
>>
>>It always pops up. It's part of the print engine regardless where
>>output goes.
>
>Gotcha ... but not so good for us. :-)
>Thanks,
>Bill

I beg to differ: REPORT FORM X TO FILE Y ASCII does not bring up the "Printing..." dialog. Without the ASCII clause it does bring up the dialog.

Also, what about the sqlexec()?

I did find in Rick's "Using VFP COM Objects with Active Server Pages" this little tidbit:

*** If you use a SQL backend use this to prevent login dialogs!
* SQLSetProp(0,"DispLogin",3)

which I will definitely set. Thanks, Rick.

^Carl Karsten

ps: interesting behavior: while running these reports, clicking on a command window, then right clicking on the VFP button of the task bar results in either a menu the width of the screen, or a gpf in explorer.exe.