Strange Record Movement

[Sean Nijenhuis]

Hi, thanks for your time.

I have a form based on a query that make use of two(2) related tables. The
form has a tab control on it, each page in the tab control representing
fields from each individual table in the underlying query.

Problem I'm experiencing is that if the a user enters information in a
record (update) when leaving the field, the user finds she's in a completely
different record.

Its like access is jumping between records.

I've checked Tab Order on the form.
I've compact and repaired the frontend as well as the backend.
I've checked the relationships. Enforced Refer. Int. Cascade updates and
deletes.
Access Version 2000. Windows XP and Windows 2000 users

Stumped.

Thanks
Sean

 

[John Vinson]

I have a form based on a query that make use of two(2) related tables. The
form has a tab control on it, each page in the tab control representing
fields from each individual table in the underlying query.

Problem I'm experiencing is that if the a user enters information in a
record (update) when leaving the field, the user finds she's in a completely
different record.

What's the Record Source of the form? And what's the tab order of the
controls on the form - could it just be moving to the next record in
the Query on tabbing out of the field?

 

[Sean Nijenhuis]

Record Source is that of the query.

Tab Order has been checked, the tab still has to move through six command
buttons before it goes through to the next record.

Thanks

 

[John Vinson]

Record Source is that of the query.

Please post the SQL view of the query. How are the tables related? If
they're one to many, you should strongly consider basing your Form on
just the "one" side table, and using a Subform based on the "many".

 

[Sean Nijenhuis]

SQL Source:
SELECT usrCandidates.CandidateID, usrCandidateInterview.CandidateID AS
InterviewCandidateID, usrCandidates.Delete, usrCandidates.FaxNumber,
usrCandidates.Title, usrCandidates.FirstName, usrCandidates.MiddleName,
usrCandidates.Surname, usrCandidateInterview.Pension,
usrCandidateInterview.GroupLife, usrCandidateInterview.MembershipFees,
usrCandidateInterview.Other, usrCandidateInterview.NextReview,
usrCandidates.TempWork, usrCandidates.TypistID,
usrCandidates.MaritalStatus, usrCandidates.Dependants,
usrCandidates.DateUpdated, usrCandidates.UpdatedBy, usrCandidates.Filed,
usrCandidateInterview.SelectionConsultantID,
usrCandidateInterview.SelectionDate, usrCandidates.City,
usrCandidates.PostalCode, usrCandidates.ETFPosition, usrCandidates.Initials,
usrCandidates.GenderID, usrCandidates.DriversLicence, usrCandidates.EMail,
usrCandidates.ETypeID, usrCandidates.RelocTypeID,
usrCandidates.AnnualPackage, usrCandidates.Rating,
usrCandidates.Currentrate, usrCandidates.Desiredrate,
usrCandidates.StatusChangeDate, usrCandidates.OrigCV,
usrCandidates.OriginalCV, usrCandidates.CategoryID,
usrCandidates.CurrentEmployer, usrCandidates.WorkEmailAddr

FROM usrCandidates LEFT JOIN usrCandidateInterview ON
usrCandidates.CandidateID = usrCandidateInterview.CandidateID;

Just a note: If i change a value say in the "surname" field, it jumps to a
completely different record but remains in the "surname" field.

Ta

 

[Sean Nijenhuis]

Thanks - tried that - it appears not to be anything to do with the Tab Order
though. It almost as if Access is simply "jumping"?

 

[John Vinson]

Just a note: If i change a value say in the "surname" field, it jumps to a
completely different record but remains in the "surname" field.

I don't see anything unusual about the query, other than that one
should generally use a Form for the "one" and a subform for the "many"
- did you deliberately choose NOT to do this? Do you have any VBA code
on the Surname textbox, or the Form's BeforeUpdate or AfterUpdate
event?

I have never seen this behavior, and I suspect that it might be one of
the wierd things that happen when forms become corrupted. You might
need to delete and recreate the form (and I'd suggest using a
Form/Subform when you do so!)