Bonjour Michael,
If we only use a filter clause to suppress rows, a work-around is to rewrite script using where clause. We used this workaround for one of our project. But for live application it is different. First, customer has first to notice that his data model changed, and diagnostic that the filter is no more working. Second he has to rewrite part of the script, and run into comparison tests before putting it in production.
But if you use other filters, like duplicate missing column data in example below, this work-around doesn't work, and the only solution is then to downgrade to SR4.... This is precisely the case for our recently installed customer.
LOAD ... FROM
[catalogue.xls]
(
biff,
header is 2 lines,
explicit labels,
table is [Sheet1$],
filters
(
Replace(3, top, StrCnd(null)),
Replace(13, top, StrCnd(null)),
Remove(Row, RowCnd(CellValue, 16, StrCnd(null)))
)
)
;
If we replace the third filter by " WHERE (len(text(@18)) > 0) ", we still need both "replace" filters (we can't change source data), and the bug still occurs.
