Well, that's pretty judgemental, Dorris. Let me offer a different opinion. I know of no other Windows apps where I have to have a separate interface to pick the printer. It's done via a std. Windows interface. That's one reason it's there. When I choose to print to a certain printer, the next time I print the program will usually reselect that printer and that's usually correct. I feel this is std. Windows behavior and I'd like to have my programs behave in this way instead of differently. I'm not try to cede control - I'm trying to get VFP or Windows to tell me what the user did so that I can understand it and make my program work in a more seamless fashion. Perhaps you don't agree with that, but that's what I think should be done.


>And there's your problem. You're allowing control of the printstream to pass outside of VFP. I liken it to getting into a cab and saying "Take me to the airport" - you have just passed control of the route to the driver of the taxi, but if you get in that cab and say "Take me to the airport via (insert route here)" - you still get to the airport, but you get there the way you wanted to get there (or, you got thrown out of the cab by a very PO'd cabbie).
>
>Yes, when you use PROMPT, you get the 'standard Windoze' way of selecting a printer and absolutely no clue of which printer was selected because you choose not to know and Windows knows this and it'll take care of your print and pat you on the head and tell you 'good dog'.
>
>If you're wanting "know the route", then you're going to have to specify the route.
>
>