Data unexpectedly posts istelf in another field

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • chuck gregory
    New Member
    • Dec 2006
    • 78

    Data unexpectedly posts istelf in another field

    I posted recently about two fields not acceptiing keystroke entries after months of trouble-free use. one of those fields is now posting entered keystrokes into the same field of another, unrelated record. I found this out by sorting for a last name, and these two showed up with about ten others that are not affected by it. Entering the single keystroke in that field in either record produces a change in the other. I have compacted and repaired the database(s), but it still happens. Any ideas?
  • puppydogbuddy
    Recognized Expert Top Contributor
    • May 2007
    • 1923

    #2
    Originally posted by chuck gregory
    I posted recently about two fields not acceptiing keystroke entries after months of trouble-free use. one of those fields is now posting entered keystrokes into the same field of another, unrelated record. I found this out by sorting for a last name, and these two showed up with about ten others that are not affected by it. Entering the single keystroke in that field in either record produces a change in the other. I have compacted and repaired the database(s), but it still happens. Any ideas?

    It is probably by design if the two fields are in different tables. You likely have relationships set up to enforce referential integrity between each of the tables underlying the two fields. Are youy sure the two table records are not related?

    If they are truly not related, then you probably need to change the relationship between the two tables via the relationship button on the toolbar.

    However, you should be aware, that a normalized relational databases like Access consists of many one-to-many relationships between the data tables. For example, consider the one to many relationship Order table and Order detail table......Each order has many details. In order to assure that the Order Details are properly matched to the correct Order, a relationship is set up and enforced on the Order#.

    Comment

    • chuck gregory
      New Member
      • Dec 2006
      • 78

      #3
      It was one table until I had the wizard analyze it. Might that have something to do wtih the problem?

      Comment

      • puppydogbuddy
        Recognized Expert Top Contributor
        • May 2007
        • 1923

        #4
        Originally posted by chuck gregory
        It was one table until I had the wizard analyze it. Might that have something to do wtih the problem?

        Yes, if you allowed the wizard to split your tables on the basis of its analysis. You need to look at the relationships window and see how your database is strucutured. If the wizard split the tables, it is not necessarily a bad thing, but you need to have some basic concept of database structures and normalization in order to know whether the wizard is making a good decision. I suggest you take the first tutorial at the following link on Database structures and normalization before proceeding.

        Comment

        • chuck gregory
          New Member
          • Dec 2006
          • 78

          #5
          Thankyou; I hope I can figure it out.

          Comment

          Working...