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...

Thank you Rob!

I have checked out PROIV Version, it's 5.5, maybe this new fields have been added to LSDEF in newer versions... . Strange...
Thank you anyway!

Hi,

I would not try to change the VIP files, the tag name is used in quite a few VIPBM??.pro files, as they now use this as a key, instread of the LS number.

Rob.

Hi Rob.

I have an LSDEF of 39 Fields... And with VIP, I can't do a Function for manage the LSDEF [Invalid File Name]... Anyone know where VIP saves the tag names for the Cycles????

Maybe you have an old version of LSDEF filedef.

Its the 78th field

Rob.

Hi Rob and Donald.

First of all, thank you for your answer, but I have checked out the file: LSDEF, and I have not seen any reference to the LS Tag. Also I have looked for a function that had LS Tags (made in VIP), and I can't see the LS Tags in this file... Is there any other file where PROIV save information relative to the LS????

Hi Ivan

Rob is quite correct.

If you have the bootstrap files AND VIP, then in VIP use the New tab of the General Object Open window and click on the file browser icon. Follow the prompts to create a browser screen for the file (LSDEF). And as Rob indicated, you can then edit the record that you need to add a tag name to. This way you're creating a VIP screen that allows you to edit the data on the file that you want to change without pulling the function itself into VIP.

Just be very careful about what you change - it's a bootstrap file. If you're not sure - then use Rob's IDE tool.

Donald

Ah - I see. sorry. Well if what you want is to produce a seq file as described
then drop the report. Use an update function instead. Create a Pro-iv
file def of type 'SEQ' with a long enough recordlength for your string of
fields. Then compose each line by reading your input files in the update
function and then LSCALL to add one record to the file at a time as required.

It may be possible to achieve what you want using pro-iv report but
it would be trickier to get right. Probably you would create a report header
composed of your master fields and use that as the associated header
for your detail cycle. And in the detail cycle you could print out the detail
fields. But I think the UPDATE function is what you're after.

This solution works fine!!!, thank you very much for your answer...!!! Now my, problem is how to explicit the structure to EXCEL with DDE commands in order to able the user to contract and expand the detail nodes...