Mary, to confirm, yes it's assumed readers with preceded by a map is parameterised (and uses the standard expando syntax).
If you really need a like statement then you can use the CHAR (or equivalent sql function) for %.
select * from ARCUS where NAMECUST like 'R' + CHAR(37)
Realisable Software Ltd provides code-free, cost-effective applications integration solutions for SMEs. Our core IMan product is designed to integrate almost any application with a number of Sage solutions and online payment processors.
Looking to purchase IMan, please see our resellers here.
Realisable Software
Ph: +44 (0) 208 123 1017
Copyright © Realisable. All rights reserved.
Realisable is a registered trademark
Realisable Software Ltd provides code-free, cost-effective applications integration solutions for SMEs. Our core IMan product is designed to integrate almost any application with a number of Sage solutions and online payment processors.
Looking to purchase IMan, please see our resellers here.
Realisable Software
Ph: +44 (0) 208 123 1017
Copyright © Realisable. All rights reserved.
Realisable is a registered trademark
Realisable Software Ltd provides code-free, cost-effective applications integration solutions for SMEs. Our core IMan product is designed to integrate almost any application with a number of Sage solutions and online payment processors.
Looking to purchase IMan, please see our resellers here.
Realisable Software
Ph: +44 (0) 208 123 1017
Copyright © Realisable. All rights reserved.
Realisable is a registered trademark
I have a job with a dbreader, a map and then another dbreader.
In the second dbreader, the WHERE clause includes ...AND SH.REFERENCE not like '%EDI%', which gets the following error: "Error whilst generating the parameterised select statement. LIKE statements on parameterised select statements are not supported and should be replaced with equivalent SQL functions. Error - The field [EDI%' ] does not exist."
Is a dbreader which follows a map always assumed to be parameterised or is there a way to tell it that it is not? Or is it simply that you can NEVER use LIKE in a dbreader if it is not the first transform?
If the latter, please change the error message to something like "...LIKE statements in select statements following any other transform are not supported...". Please also add this information to the discussion of parameterised db readers in the manual.