C
Christine
I am trying to set the ValidationRule for a table field using DAO but
get an extra character at the end, that I cannot get rid of. For
example:
fld.Properties("ValidationRule") = ">0" results in 3 characters being
in the property. The first two are correct (">0") but the extra
character is an ascii 48, which shows up as a box when I hover over
the value in debug mode.
In searching the newsgroups I have seen complaints of an extra chr(0)
at the end of the ValidationRule. I don't believe that is the same as
the ascii 48, but maybe it is. In any case, there does not seem to be
any way for me to correct this. But it is causing programmatic
problems, and driving me absolutely crazy. It seems like it must be an
Access bug.
Does anyone know of a solution for this? None of the chr(0) posts I
saw had a solution. I can't believe how ridiculous this problem is and
would really appreciate help. Please help me if you can.
I am using Access 2000. Is there any other way to set the
ValidationRule programatically? And/Or, if this is a bug, is it fixed
in Access 2002? or 2003?
Thanks in advance.
Christine
get an extra character at the end, that I cannot get rid of. For
example:
fld.Properties("ValidationRule") = ">0" results in 3 characters being
in the property. The first two are correct (">0") but the extra
character is an ascii 48, which shows up as a box when I hover over
the value in debug mode.
In searching the newsgroups I have seen complaints of an extra chr(0)
at the end of the ValidationRule. I don't believe that is the same as
the ascii 48, but maybe it is. In any case, there does not seem to be
any way for me to correct this. But it is causing programmatic
problems, and driving me absolutely crazy. It seems like it must be an
Access bug.
Does anyone know of a solution for this? None of the chr(0) posts I
saw had a solution. I can't believe how ridiculous this problem is and
would really appreciate help. Please help me if you can.
I am using Access 2000. Is there any other way to set the
ValidationRule programatically? And/Or, if this is a bug, is it fixed
in Access 2002? or 2003?
Thanks in advance.
Christine