J
John Morrelles
I've used UNION queries in combo row sources for years to provide a
"None" or "All" choice at the top of the combo box list like this:
SELECT "<All>", Null FROM tblStatus UNION SELECT StatusDescription,
StatusID FROM tblStatus ORDER BY StatusDescription
As users have moved from Access 97 to Access 2002 and 2003, my
applications are breaking because the result set for the combo box is
corrupted. The column where I specify the Null for the first row
contains corrupted characters, like wingdings, rather than the numeric
ID values that should be there.
Has anybody else experienced something like this? I'm having to go
through my combo boxes and change the Null to an empty string ("") and
rewrite my code to look for empty strings rather than checking for
IsNull.
"None" or "All" choice at the top of the combo box list like this:
SELECT "<All>", Null FROM tblStatus UNION SELECT StatusDescription,
StatusID FROM tblStatus ORDER BY StatusDescription
As users have moved from Access 97 to Access 2002 and 2003, my
applications are breaking because the result set for the combo box is
corrupted. The column where I specify the Null for the first row
contains corrupted characters, like wingdings, rather than the numeric
ID values that should be there.
Has anybody else experienced something like this? I'm having to go
through my combo boxes and change the Null to an empty string ("") and
rewrite my code to look for empty strings rather than checking for
IsNull.