Hi George,
I need to divide this message, the first part is a big problem to me. The other part - let's say I feel uncomfortable with to many kludges.
----------------------------------------------------------------
Important part:
>
>SET PRINTER TO NAME < Windows Printer Name > won't work for you?

AFAIK < Windows Printer Name > must be known to me. I can get it from APRINTERS() but which one is the one the user need?

I like the dialog from CommonDLG because I can adjust all printer settings and answers (even strange) to Cancel.

call_CommonDLG
SET PRINTER TO NAME Windows_Printer_Name

is a good idea - but where I get the name of the printer I selected in CommonDlg?

Oh lord, all what I need is a dialog as simple as in MSWord
- Print.Click -
- Dialog - select printer, set printer's prop's -
- (ok.Click -> Print) or (cancel.click -> no print)-

no change of Windows default printer, no strange new form to adjust printer (like GETPRINTER()) just good old window style dialog that is the same like everywhere else in the system.

--------------------------------------------------------------
Philosophical part:
>
>Just one comment about what you mentioned above (for both you and the customer). After Win98 the Windows Script Host isn't optional. IOW, if you ever upgrade Windows, it's going to be there. There is nothing "evil" about it, except that some people of highly questionable ethics, have used it to create worms.

Got an idea why I stuck on WIN98?
You know 11th law? Do never update or upgrade. ::)

There is no evil in weapons too. But without it is harder to kill somebody. We have those 17 dead in our scools now - The mad boy would hardly reach this goal with a kitchen knife.

Those people you talk about are sitting in federal offices? Or do you mean all the little things are hidden in HTLM code? There is more than a worm what can go wrong with WSH.

WSH is a open door for each and everybody that need to be closed.

>
>Basically, the choice for both you and your customer is either stick with outdated and eventually unsupported technology, or not. The WSH isn't going away anytime soon. I wrote a "Postscript" article on the original WSH series for the VFUG newsletter that appeared last year. In it, I discuss these issues and what you can do about it.

If something is outdated or not is not the question of available new gadgets. It's only in our mind.
Please understand me, it is not that I like the time before exploration of open fire, it is simply not needed yet.

And if we start the "technology" debate, I know a lot of people (not me) feeling the whole idea of a foxpro database outdated because we have those SQL servers and the whole idea of a wintel PC as well...

Foxpro is a giant on new "technology" now, we finaly got a GETDIR() dialog that gives us control over UNC resources. We can not place it on the srceen where we need it but I don't want to argue.

We stuck on tiny 16*16*16 icons for our apps uggly as on WIN3.0 - no I feel happy with this "technology".

We got new things to play with on VFP 7.0 but the fox will never learn how to react on ALT+F4 until we give some strange commands in the code. How many apps are out there without "ON SHUTDOWN"?

There are hundreds of things working not as appriciated under Windows in VFP - there are reasons in the way Foxpro is and probably this way is more important to us. But on some days this is not off help. ::(


Agnes