4 replies to this topic

[Ivan Gomez]

Hello to everyone!

I am facing a problem with the instruction CLIENT.EXECTUE in VIP and Windows XP/2000. I have a program that makes a sequential file. The program takes long time to perform all the extraction (about 1 hour). When the seq file is finished, I perform a FTP to get it into the client. but when I perform the instruction to check if the local directory exists (See Codebox), the function remain stuck. I can see the window opened (C:\adm\) but the program is not able to continue executing the following instructions.

[codebox]  #S = client.execute('c:\adm\','','SW_SHOW') [/codebox]

When I execute the program with less data and the extraction takes about 20 - 25 minutes, the problem doesn't appear and it works correctly.

Any Idea?
Thank you Very Much!!

[Donald Miller]

Hi Ivan

Is CLIENT.Execute not for "executing a file on the Windows client"?

The manual says that "if filename has an extension other than '.exe', the Windows client will automatically find the program to execute the file"

So it's expecting to run something and the filename "c:\adm\" in your example has no extension so maybe it's still looking....

[Ivan Gomez]

Hi Ivan

Is CLIENT.Execute not for "executing a file on the Windows client"?

The manual says that "if filename has an extension other than '.exe', the Windows client will automatically find the program to execute the file"

So it's expecting to run something and the filename "c:\adm\" in your example has no extension so maybe it's still looking....

Hi Donald...

No, The windows client opens an explorer located on the directory c:\adm\... but the proiv client get stuck. It only happens when the extraction is running more than 40 - 50 minutes... When the extraction is small, everything goes fine...

[George Macken]

Hi

I would suggest UMSGing around the calls, or turning on trace to see where things are stopping, and that could contribute significantly to the time taken to get to the problem

Using a trial function - try transferring files of different sizes - increasing by 10K for example each time - at what point size-of-file does it break - is it always consistent in stopping once a particular fiel size is reached?
Is there lots of free space on both server and client-machine for the file.
Are there any security restrictions/firewall that are been passed thru that limit the size of files allowed ?
Is there a file of same-name already present on the client-machine, would it cause a problem

Rgds

George

[Rob Donovan]

For clarification, Client.Execute seems to behave like the 'Run...' option in the windows 'Start' menu....

So, just putting a dir name, will open that dir up in explorer.

Rob.