J
Joe
We have a relational database (two tables) from which we
generate a query, which is used to generate labels and
forms. The db was created in Access 2000 and converted to
Access XP. The problem arises when the field/column of
data contains multiple codes seperated by commas, such as
01a,01b,etc. The query process works in both 2000 and xp
versions using the criterion (like "01a") which only
selects the records with a single code and the merge is
successful. But using wildcards in the XP version
(like "*01a*") which works in 2000 versions, to select
records in the column which have multiple codes seperated
by a comma delimiter such as 01a,01b in the record field,
causes the merge to fail and be completely blank on an
otherwise successful query. Does anyone know if wordxp
code is not written to utilize wildcards (*) or prefers an
alternative delimiter to commas.
generate a query, which is used to generate labels and
forms. The db was created in Access 2000 and converted to
Access XP. The problem arises when the field/column of
data contains multiple codes seperated by commas, such as
01a,01b,etc. The query process works in both 2000 and xp
versions using the criterion (like "01a") which only
selects the records with a single code and the merge is
successful. But using wildcards in the XP version
(like "*01a*") which works in 2000 versions, to select
records in the column which have multiple codes seperated
by a comma delimiter such as 01a,01b in the record field,
causes the merge to fail and be completely blank on an
otherwise successful query. Does anyone know if wordxp
code is not written to utilize wildcards (*) or prefers an
alternative delimiter to commas.