Results 1 to 4 of 4

Thread: #name?

  1. #1
    Join Date
    Sep 2009
    Posts
    1

    Unanswered: #name?

    Hello,

    I have designed an Access 2007 database for use within our office. It is a split database with the tables in the back end and each user running their own copy of the front end.

    I have a report in there which pulls a few fields into a letter. Everything works fine for me and most of the other users, but for a couple of people they see #name? where one of the fields should be. This is puzzling me, as I thought it there was an error it would be the same for everyone. It's also quite hard to fix, when it's working fine on your machine.

    The field in question is a text box with some simple code to format the address and leave out any blanks.

    =IIf(IsNull([O_ADDRESS1]),"",[O_ADDRESS1] & Chr(13) & Chr(10)) & IIf(IsNull([O_ADDRESS2]),"",[O_ADDRESS2] & Chr(13) & Chr(10)) & IIf(IsNull([O_ADDRESS3]),"",[O_ADDRESS3] & Chr(13) & Chr(10)) & IIf(IsNull([O_ADDRESS4]),"",[O_ADDRESS4] & Chr(13) & Chr(10)) & IIf(IsNull([O_ADDRESSCity]),"",[O_ADDRESSCity] & Chr(13) & Chr(10)) & IIf(IsNull([O_ADDRESSPOSTCODE]),"",[O_ADDRESSPOSTCODE] & Chr(13) & Chr(10)) & IIf(IsNull([O_ADDRESSCOUNTRY]),"",[O_ADDRESSCOUNTRY])

    Any thoughts as to why I might be getting #name? for some users and not others would be most helpful.

    Thanks in advance.

    Dave.

  2. #2
    Join Date
    Nov 2004
    Location
    out on a limb
    Posts
    13,692
    Provided Answers: 59
    #name occurs when the query parser doesn't recognise a column or function.
    so check and recheck the spelling if any columns or functions

    or alternatively break apart your expression and then try sectionby section to findwhere your typo is
    I'd rather be riding on the Tiger 800 or the Norton

  3. #3
    Join Date
    Jun 2005
    Location
    Richmond, Virginia USA
    Posts
    2,763
    Provided Answers: 19
    Are all users running the same version and service packs as you are on the development machine?

    You also need to check the errant machines to see if references are missing.
    Hope this helps!

    The problem with making anything foolproof...is that fools are so darn ingenious!

    All posts/responses based on Access 2003/2007

  4. #4
    Join Date
    Dec 2004
    Location
    Madison, WI
    Posts
    3,926
    Check to make sure there aren't any missin references on any machines or references that should be in the listing but are not. This often plays a part on expressions if the incorrect reference is used.

    Check the MDAC version on both machines.
    Expert Database Programming
    MSAccess since 1.0, SQL Server since 6.5, Visual Basic (5.0, 6.0)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •