A user called yesterday and said that one out of three reports that they run regularly was not working. At first, there was a network rights issue, as the user did not have write rights on the volume where the report file was being created. Easy enough to fix.

However, the file is now being created, but it is not being printed.

I think I finally tracked it down to the fact that the non-functioning report is using PCPERFORM, while the two reports that do work use PCEXECUTE.

In the R/Basic manual, it is stated that the COMSPEC DOS variable must be set in order to use PCPERFORM. Understandable, it has to know where the command interpreter is. Apparently, PCEXECUTE does not have this "limitation".

As I cannot seem to find any documentation on PCEXECUTE, I would like to ask a couple of questions. Performance wise, how do these two functions match up? Also, what about memory usage? Are the differences similar to the differences between SUSPEND and PC EXIT from the TCL?

I'm trying to decide if I should just make sure that all of my users have COMSPEC set, or if I should identify all of my programs that PCPERFORM and change them to PCEXECUTE.

Any pointers one way or the other would be appreciated.

Thanks!!!

msorrel@greyhound.com

We used to have this problem when I was at network support for Wordperfect.

Have the user type "set" at the dos prompt. If comspec isn't first then you could have this type of problem.

I would check the login script (assuming Novell) or the autoexec.bat for the comspec command. It really isn't neccessary in this day and age when machines are using windows and not getting the command.com from the server.

rem the statement and see if that helps.

Dale

Matt,

We always use SUSPEND EXIT then the operating system command.

This is due to memeory issues and we accepted the advice of

Revelation user material which highlighted this for us.

When you use NT Workstations you need to set printers this way

rather than using the net use statements as part of the voc entry.

Within Win95/98 scenario the net use statements (with NT Server) may

execute from the voc entry.

Hope this helps.

Regards,

Kevin Gray

Graycorp

(email kevin@graycorp.com.au)

PCPERFORM and PCEXECUTE are the same opcode. Would have to be comspec issue or something related.

The Sprezzatura Group

[/i]World leaders in all things RevSoft[/i]

View this thread on the forum...