We have an existing exchange scheme and have tried to add a condition to prevent a record being exported. This means a condition attached to the table relations.

However, the values of the table fields, do not feed through to the script. I know that it is picking up the latest version of the script, as it has been tested by just passing a boolean of false and this rejects all the records as required.

The table is declared at the start of the condition script.

We notice in debug that the select on the table to retrieve the data for export, only selects the fields defined. However while running a different exchange scheme in debug, we see that the select retrieves all table fields ; tablename.*

Can anyone help ? Is there a procedure or setting that we are missing ? The table has recently had a new field added, but I cant see this being the problem.

Thanks

Hi,

You must insert all fields in "Maintain Paramets by Condition", that you want check in your conditionscript. I mean the fields of the table, that you want to export. You don´t need to define the table again in the script.

Sorry, but I cannot set the field up as a parameter, as it is not defined on the ascii file, (It is not required on the ascii file). This doesnt explain why in a different exchange scheme, the values of the table fields show up when the condition script is in debug.

Thanks for your help anyway.

Although I don't like exchange and hardly ever used it, you mentioned that the table in question was modified recently (fields have been added). So you should regenerate the exchange script, as these fields will not be read now. If the field you want to check is one of the new ones, this for sure is the reason. If it isn't, this still could help (don't trust exchange further than you can throw it)

regards

Norbert

Thanks for your help (both of you). I had created the export script, but there was still a problem. However the new field was added to the ascii file definition (with a field length of zero) & added to the table field relations. This was then set up as a parameter and then could be checked by the condition script.

I still dont understand how any actual table fields cannot be checked in the script, but in another exchange scheme they could.


Thanks