Results 1 to 14 of 14
  1. #1
    Super Moderator
    Join Date
    Jun 2002
    Location
    Mt Macedon, Victoria, Australia
    Posts
    3,993
    Thanks
    1
    Thanked 45 Times in 44 Posts

    Bizarre Behaviour (2003)

    I think this is bizarre.

    I have a db that tracks children/families involved in a research study. Each child has a status, that starts as "invited", and that is the default value for the table. Status is just a text field.

    The moment any data is entered for a new child, into any field, the value of status changes automatically to "not enrolled", and I can't find anything that explains why.

    "Not Enrolled" is not even one of the values in the lookup table for status.

    You would expect that there is some form level event triggered by entering data, but I can't find any. I do a search for "not enrolled" within the whole project, and it is not found.

    I deleted the status field from the table and the form, and could enter records without any errors occurring. (if there was some code somewhere that I had not found, I thought this would bring it to light with an error.)

    The moment I put them back the error came back.

    I imported both the front end and back end files into new empty databases.

    I suspect that there is some corruption in the form, and I need to rebuild it from scratch, but I am hoping not to have to.

    Any thoughts on anything else to try?
    Attached Images Attached Images
    Regards
    John



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

    Re: Bizarre Behaviour (2003)

    The phrase "Not enrolled" must have an origin - as far as I know it's not a built-in Access term, so I don't see how a corrupt form or table could cause this phrase to appear.

    Any chance of posting a stripped down copy of the database?

  3. #3
    Super Moderator
    Join Date
    Jun 2002
    Location
    Mt Macedon, Victoria, Australia
    Posts
    3,993
    Thanks
    1
    Thanked 45 Times in 44 Posts

    Re: Bizarre Behaviour (2003)

    Thanks

    It will take bit of work to extract the bits that can be posted, but I will have ago at it. I imagine that as I extract them, the problem will go away!
    Regards
    John



  4. #4
    4 Star Lounger SteveH's Avatar
    Join Date
    Jan 2001
    Location
    Chelsea, Gtr London, United Kingdom
    Posts
    587
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Bizarre Behaviour (2003)

    Long shot here - have you checked the table properties? I've had things 'hide away' in there that I've forgotten about.
    Just a thought. <img src=/S/shrug.gif border=0 alt=shrug width=39 height=15>
    Steve H
    IT Lecturer/Access Developer
    O2K SR3/O2010; Win7Pro

  5. #5
    Super Moderator
    Join Date
    Jun 2002
    Location
    Mt Macedon, Victoria, Australia
    Posts
    3,993
    Thanks
    1
    Thanked 45 Times in 44 Posts

    Re: Bizarre Behaviour (2003)

    Thanks for the suggestion.

    I have looked there, and can't see anything. The problem only happens if I enter data through the form. I can enter a record directly into the table without problem.
    Regards
    John



  6. #6
    Gold Lounger
    Join Date
    Feb 2001
    Location
    Sint Niklaas, Belgium
    Posts
    2,778
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Bizarre Behaviour (2003)

    Did you try to delete and recreate the lookup table for Status ?
    When you delete the field from the table and the control from the form, did you recreate them with other names or with the same names ?
    My <img src=/S/2cents.gif border=0 alt=2cents width=15 height=15>

    If you want I have a look at the db, you can send it to my e-mail address (see my profile)
    Francois

  7. #7
    Super Moderator
    Join Date
    Jun 2002
    Location
    Mt Macedon, Victoria, Australia
    Posts
    3,993
    Thanks
    1
    Thanked 45 Times in 44 Posts

    Re: Bizarre Behaviour (2003)

    Thanks Francois

    I just deleted the field and the control again, then recreated them with different names. Problem gone. It worked.
    Then I renamed the field back to Status, and the problem reappeared.

    Then I deleted the lookup table completely, and it made no difference.

    Now I have renamed the field back to "ChildStatus" and the problem has gone again.

    I need to bring out "Find and Replace" so I can leave the field name at "ChildStatus".

    Earlier I made a very rudimentary new form based on the same query, and it worked OK. So I still think it is something wrong with my form somewhere.
    Regards
    John



  8. #8
    Gold Lounger
    Join Date
    Feb 2001
    Location
    Sint Niklaas, Belgium
    Posts
    2,778
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Bizarre Behaviour (2003)

    I tested this in the VBA editor :
    If you write status on a line and go to the next line, status is changed in Status.
    So I think Status is a reserved word, and that is never a good idea to use reserved words as field or control names. Maybe is that the problem.
    I can't search it in the help file as my help file is not working.
    Francois

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

    Re: Bizarre Behaviour (2003)

    If I try that, status is not changed to Status, and Status is not in the List of reserved words in Access 2002 and in later versions of Access...

  10. #10
    Gold Lounger
    Join Date
    Feb 2001
    Location
    Sint Niklaas, Belgium
    Posts
    2,778
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Bizarre Behaviour (2003)

    Then I don't know where the error is. <img src=/S/shrug.gif border=0 alt=shrug width=39 height=15>
    Francois

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

    Re: Bizarre Behaviour (2003)

    I don't either... <img src=/S/sad.gif border=0 alt=sad width=15 height=15>

  12. #12
    Platinum Lounger
    Join Date
    Dec 2001
    Location
    Melbourne, Australia
    Posts
    4,594
    Thanks
    0
    Thanked 27 Times in 27 Posts

    Re: Bizarre Behaviour (2003)

    Any chance of the database for me to have a peruse John?

  13. #13
    Silver Lounger
    Join Date
    Jun 2001
    Location
    Niagara Falls, New York, USA
    Posts
    1,878
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Bizarre Behaviour (2003)

    Long shot

    Office 2003 may be configured to update automatically via Microsoft Update, this has caused me many problems with my client base with strange behavior with combo boxes

    There is a bug in Access 2003 (11.8166.8172) SP3

    There are a couple of bugs in Office 2003 SP3, and I've listed them in a yellow div at the top of this page:
    http://allenbrowne.com/tips.html

    Description of the Access 2003 post-Service Pack 3 hotfix package: December 18, 2007

    http://support.microsoft.com/kb/945674

    Access 2003 (11.8204.8172) SP3 OK after hot fix

    HTH, John

  14. #14
    Super Moderator
    Join Date
    Jun 2002
    Location
    Mt Macedon, Victoria, Australia
    Posts
    3,993
    Thanks
    1
    Thanked 45 Times in 44 Posts

    Re: Bizarre Behaviour (2003)

    Thanks for the various suggestions.

    The db is quite large and contains some private data so I can't post the whole thing. I have just made a cut down version but it does not display the same problem.

    I wondered about Reserved words. Status is not listed on Allen Browne's list of Reserved words

    I also wondered if it might be a combo box problem, so when I replaced the control (after deleting it) I put it back as just a text box. There are still a few other combos around though.

    I am in the process of getting and installing the hotfix.
    Regards
    John



Posting Permissions

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