Do you think the easiest way to handle this would be to simply switch that field to a varchar(4), so that it could properly add '%' to the search parameter value ?
Thanks,
Robin Giltner
'-- Set the size on the parameter
loReturn.Size = QueryInfo.FieldLengths(FieldName)
to
loReturn.Size = QueryInfo.FieldLengths(FieldName) + 2
And this seems to have fixed our problem of using all possible characters on a Contains search in the BrowseDialog.
Thank you guys.