IIF in the Control Source property of a txtbox

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • djchaney3
    New Member
    • Jan 2014
    • 7

    IIF in the Control Source property of a txtbox

    Hello all. I have created a txtbox to display data based on another control. When I close my database and reopen it the txtbox displays #Name?. The odd thing is, if I change the name of the txtbox it will display IOP COUNT as I need it to, untill I shut it down and open it back up. I am not sure if there is anything I am doing or if it is a bug.

    Below is the code in my txtbox.
    =IIf([Request Type]="OBS/SUP","IOP Count:",Null)
  • jimatqsi
    Moderator Top Contributor
    • Oct 2006
    • 1293

    #2
    We had something like this pop up a few months ago ... what is in the Default property of your text box?

    And what do you mean by " if I change the name of the txtbox "? I think you mean something else, not actually changing the name of the text box object.

    Jim

    Comment

    • djchaney3
      New Member
      • Jan 2014
      • 7

      #3
      When looking at the property sheet, on ALL the first line (Name) when I change that the formula works, untill I shut the program down again and open it up.

      The Default value is blank

      I am the only one this affects it appears. 9 of us use this database and yet it only affects me. I have 6 people on Win7 Access 2010 and 3 of us are on XP Access 2007. It may be my PC I assume some setting maybe?

      Comment

      • zmbd
        Recognized Expert Moderator Expert
        • Mar 2012
        • 5501

        #4
        Using two different versions of Access on the same database is a guaranteed disaster waiting to happen!

        The different OSs are not as much of an issue.

        It has been a year or more ago that I seem to remember another member having something simular happening. It turned out that they also had different versions of Access opening and closing the same database. It seems to me that the solution was to split the database and push a copy of the front-end down to each client PC.

        Comment

        • djchaney3
          New Member
          • Jan 2014
          • 7

          #5
          The rest of my team will be migrated to the new versions within the next week or so. I will wait to see if this clears it up.

          We are already using a split database with a front and back end. I am assuming the issue is something with my PC or software as it only happens to me. Thank you for all of your assistance.

          Comment

          • NeoPa
            Recognized Expert Moderator MVP
            • Oct 2006
            • 32661

            #6
            It's definitely worth making a separate copy for those using a different version. Using a different version than the one it was designed on typically causes changes to be made that are not consistent with the original. I've learned that one the hard way.

            Comment

            Working...