Re: SYSTEM command in stored procedures [2338]

Hi Alain, I have the Solaris platform as main system but i debug and test our database and softwares on NT platform as well. I managed to get the esqlc error in my previous mail while testing in NT. I had the program called in a cmd file. Since the batch file is type of cmd, the error produced was still on screen until i press interrupt. (As you said, this way was a useful way to clarify the error produced..I agree with you.) The same scripts do not open a new console in Solaris platform. All the SYSTEM command operations are run at background. Since that, i think that the appearing black console in NT platform is because it is on NT. And the way to not to see the black console, users should write and compile an .exe file which does the events with no screen. (You can do that by Visual Basic etc..) Because i dont know a way to run .bat or .cmd files in background. Regards, Sadi ----- Original Message ----- From: "Grumelart, ...." <agrumela@foxboro.ca> To: <ids@iiug.org> Sent: Thursday, December 11, 2003 12:54 AM Subject: SYSTEM command in stored procedures [2338] | Hi | | I am using IDS on Windows NT | When I run a stored procedure that executes the "system" command, | it displays a command prompt window on the desktop. | | That may be usefull for trouble-shooting but it's not very acceptable | in a user environment. | | Is there any way to configure the IDS engine to create minimized or even | better | invisible windows with the system command ? | | thanks | | Alain Grumelart | Invensys Process Systems Inc. | | | | sending to informix-list