There are 2 ways I can reproduce the crash:

1) invoke any code that does a REPORT FORM someReport.frx TO PRINTER PROMPT NOCONSOLE or REPORT FORM someReport.frx PREVIEW

2) go into their report writer (Foxfire); as part of it's loading, it saves the current environment and it crashes each time on (which is an array with a whole bunch of system settings to be restored when the report writer exits):

ff_savsets[35] = WFONT(3,"")

- I can print a test print from the default printer via "Printers and Devices" which I take it is what you mean

- users use their own account to log into the RDC server; the only thing shared is the FPTemp directory but have not had a problem with this in the past (the RDC server is not high usage, usually only 1 or 2 people on it at a time).

I am wondering if I should just ask their system admin to reboot the server as this seems like a weird error such that (perhaps) temp files cannot be created or printers accessed from within VFP or something.

Albert



>What do you mean, "printing *anything* on the RDC"? The usual scenario is remote printing i.e. print jobs created in the RDC session are redirected to the user's local printer.
>
>Whichever printer you're printing to, within a session can you go into the printer properties sheet and print a test page?
>
>Are the RDC session users logging on with separate user accounts? I've seen weird stuff happen if multiple users log on to an RDC server using the same account.