George,

>I don't use the PROMPT clause ever. To me it's useless. All of my reports are generated from dialogs. Using the PROMPT clause simply would be aggavating to the users, since they've already made their choices (date, range, output, etc.) That doesn't mean, however, that someone else might find it useful.

How do you let the users change the printer setting ? (now done with the properties button in the PROMPT dialog). Do you simply omit these or do you provide another mechanism ?

>What about a way to determine if the cancel button has been pressed in a SYS(1037) dialog ?

Here again, how can users set the advanced properties of printers ?

>Lastly, there are some things that simply aren't going to make because that functionality (albeit in this case through an ActiveX control) already exists. There are other things that won't happen because that's not the way Windows works. For example, if someone wished for a function to determine whether or not the printer was on-line or not, that wouldn't make it. That's because Windows doesn't know (or care) until something is sent to the printer.

I certainly agree on this. I use the common dialog ActiveX whereever possible. But for example in VFP we have very little control on advanced printer settings. Until this is provided I'll use the SYS(1037) and PROMPT clause because there is simply no alterative when it comes to advandes printer settings (Documentproperties).

I certainly want to so some enhancedments on this matter, though I'm not sure how this should be implemented. For this same reason I'n very happy with the implementation of CR reports functionality into my baseclasses, which has more control over this matter.

Walter,