ACC: Unable to Use Hexadecimal or Octal Values in PropertiesLast reviewed: May 28, 1997Article ID: Q97772 |
The information in this article applies to:
SYMPTOMSAdvanced: Requires expert coding, interoperability, and multiuser skills. You cannot use hexadecimal or octal values referenced as &Hxxxx (for hexadecimal numbers) or &Oxxxx (for octal numbers) in the properties of a control.
CAUSEMost control properties expect either a string expression or a decimal number.
RESOLUTIONUse decimal numbers rather than hexadecimal or octal numbers. To determine the decimal equivalent of a hexadecimal or octal number, enter that number in the BorderColor property of a control (first write down the original value of the property so that you can easily restore it). Microsoft Access converts hexadecimal and octal numbers (&H or &O format) entered in the color properties of a control to decimal numbers.
MORE INFORMATIONIf you enter a hexadecimal or octal number in a control property that expects a string expression (for example, ValidationRule), Microsoft Access converts what you entered to a literal string. If you enter a hexadecimal or octal number in a control property that expects a number with the Long Integer data type (for example, BackColor), Microsoft Access converts what you entered to a decimal number. The following steps demonstrate how this applies to parameters that you may want to pass in a function.
Steps to Reproduce Behavior
|
Additional query words: hex oct
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |