Microsoft KB Archive/96105

{|
 * width="100%"|

PRB: Leading Space in Property Sheet Entry May Cause Error
'Article ID: Q96105

Creation Date: 08-MAR-1993

Revision Date: 01-DEC-1996' The information in this article applies to:


 * Microsoft Access versions 1.0, 1.1, 2.0, 7.0, 97

SYMPTOMS

Moderate: Requires basic macro, coding, and interoperability skills.

You have a valid value for a control that Microsoft Access does not recognize as valid. For example, you receive a &quot;#Name&quot; error value for a control that is bound to a field in the underlying table when you know for sure that the field exists.

CAUSE

The behavior may occur because you have a leading space as part of the entry for that property. For example, you may have a ControlSource property for a control that correctly identifies the name of a field for the control, but includes a leading space. In such a case, Microsoft Access attempts to include the leading space as part of the value you specified for the ControlSource property.

RESOLUTION

Remove the leading space.

MORE INFORMATION

Steps to Reproduce Behavior


 * 1) Create a new form in the sample database Northwind.mdb (or NWIND.MDB in Microsoft Access 1.x and 2.0) based on the Categories table.
 * 2) From the fields list, drag the Description field to the form.
 * 3) With the Description field in focus, open the property sheet and put a space in front of the &quot;Description&quot; value that appears for the ControlSource property.
 * 4) View the form in Form view. Note that &quot;#Name&quot; appears for the Description field even though it is part of the underlying table.
 * }

-

"THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED &quot;AS IS&quot; WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY." '' ©1997 Microsoft Corporation. All rights reserved. Legal Notices.

''

KBCategory: kbusage

KBSubcategory: FmsHowto

Additional reference words: 1.00 1.10 2.00 7.00 97 8.00