>>>Hi...
>>>
>>>I just noticed if you do the following commands one after the other
>>>
>>>sys(1037)
>>>getprinter()
>>>
>>>
>>>you get a c00005 error.
>>>
>>>
>>>Anyone else notice this?
>>
>>This does not occur on W2000 RC2 and VFP6 SP3.
>>
>>Wayne
>
>I managed to reproduce the problem by selecting a network printer as my default printer and then doing the following:
>
>? SYS(1037) && Select a networked Epson Stylus and press OK
>? GETPRINTER()
>
>Caused an access violation - I debugged into it, and VFP6 had attempted to write to memory somewhere in a system segment; without more investigation, I'd guess it's a GDI location.
>
>This didn't happen when i had a local printer selected, so I still suspect the driver may have something to do with it.

Hey Ed,

I didn't get this with a network printer under Win98 SE. Further, I'm not sure it's drive related since the printer was an HP Laser Jet 4 Plus, with one of their wonderful drivers installed < bg >.

Since the problem seems to be related only to NT, and since both functions are making calls to COMDLG32, that may be the source of the problem. The MS KB article Q220157 documents that GETPRINTER() behaves differently under Win9x than NT. That indicates further to me that the problem may actually lie in the call to the DLL.