Why is data going into different rows in the same record?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Stephen Marcus
    New Member
    • Aug 2010
    • 1

    Why is data going into different rows in the same record?

    We are new to ACCESS and are working from a form with 5 tabs for 5 pages. In one of the tabs for a single record, we will enter the data. When we go out and come back into that record, the data is gone. If we tab forward through a full cycle of all the fields, the Record field will change (possibly to Auto Number) and the information will return. When we look on it on a table, we may find the following:
    ID # 1, Record 1 - Data
    ID #1, Record 2 - Other Data from the same page

    For other tabs, the data seems completely aligned.

    I don't know if this is clear enough or makes sense, but can you explain why this is happening, and what we can do about it, or whether it's normal and OK? We are concerned that data should be aligned is actually going into different records, and that when we come back and add additional data, the alignment may continue to be off.

    Again, we are new to this, and any clarification you can provide will be very much appreciated.

    Thanks for your assistance.

    Steve
  • NeoPa
    Recognized Expert Moderator MVP
    • Oct 2006
    • 32653

    #2
    I've moved this thread across to the Access forum. You wouldn't be likely to get much help for it in MySQL, as they're all MySQL experts in there.

    Comment

    • NeoPa
      Recognized Expert Moderator MVP
      • Oct 2006
      • 32653

      #3
      Hi Stephen. Welcome to Bytes!

      This isn't actually that clear, but what seems clear is that you are having tab control (page) issues. The thing to remember is that pages are simply a way of viewing more data on the same form. Consider them like a big form folded over and over on itself (concertina-ed) and, as you may already know, whenever you move from one record to another on an Access form, the first is saved away.

      I suspect the operator may be saving away the record before it's properly ready. Maybe some Form_BeforeUpda te() code is needed to control what the operator can do. Perhaps disallowing navigation to another record except when a particular page is showing, or unless certain fields (controls on the form) have had data entered.

      Just some things to consider.

      Comment

      Working...