Results 1 to 5 of 5
  1. #1
    2 Star Lounger
    Join Date
    Jun 2005
    Location
    Atlanta, Georgia, USA
    Posts
    208
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Fields that have error message (2003)

    I have a form that has some unbound calculation fields and upon opening the fields say error becasue they are base on fields that haven't been populated yet. I can't do is error based on field an set to ""due to circular referance. If I do an onload event and set field to null the value that would conflict fields that already have data. What should I do?

  2. #2
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Fields that have error message (2003)

    Usually, Access resolves this by updating calculated fields several times during the opening of a form, so I don't know why you get an error.

    Could you post a stripped down copy of your database? See <post#=401925>post 401925</post#> for instructions.

  3. #3
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Fields that have error message (2003)

    This sometimes happens because you have dragged a field onto the form and then tried to set the source of the control to a calculation that uses the field name. Make sure you rename the control to something besides the fieldname when you make it a calculated control.
    Charlotte

  4. #4
    2 Star Lounger
    Join Date
    Jun 2005
    Location
    Atlanta, Georgia, USA
    Posts
    208
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Fields that have error message (2003)

    On opening , you can see the error fields.
    Attached Files Attached Files

  5. #5
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Fields that have error message (2003)

    You can suppress the first set of errors by setting the default value of Addinfo to "N".

    You can suppress the second set of errors by changing the control source of DDD to

    =IIf(IsNull([GWHTime]) Or IsNull([InfoFromReq]);Null;IIf([Addinfo]="n";DateAdd("h";[URAC TAT];[GWHtime]);DateAdd("h";[Left];[infofromreq])))

Posting Permissions

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