Data moving around on my subform

bryanm694

Registered User.
Local time
Today, 18:27
Joined
Jan 5, 2015
Messages
22
Hello,

I have a form on my database called frmFloorRun in which a user inputs a line number on the main form, and then in the subform they enter what will be running on that line for that given day.

Everything seems to work beautifully except that when a user clicks on a line other than line 1 and clicks the refresh button, the first item scheduled to run on line 1 will move to whatever line the user is currently on. (I apologize if that does not make much sense).

To replicate this issue: simply open the database (i have slimmed it down so that only the floor run portion is included).

Open the form [frmFloorRun] observe the first line item on line 1 (that should be what the form opens to by default).

Now click on any other line by selecting it from the dropdown (yes I realize it is a combo box, but even when I remove that combo box and enter a line number manually, the issue persists).

After selecting another line, click refresh and that first line item from line 1 will move to whatever line you have selected. This is a huge issue for our company.

Also, I have included the report that is based on this form. Feel free to open it if you wish. It simply proves that the line item does not just move on the form - it moves in the report too.

I have a feeling that this issue is somehow related to a relationship (or lack of); however, I am new enough to access that I am unable to pinpoint the issue. I think my relationships are correct but I do not really have anything to compare it to.

I appreciate any help/advice regarding this matter.
 

Attachments

I've taken a quick look, and I think your issue is that your mainform has a recordsource and your lineNo combo is bound to the recordsource - consequently, when you select a line number from this combo, you are changing the underlying record.

I think all you need to do is remove the controlsource from the LineNo combobox.
 
That seems to have done the trick! So far, it does not look like it will cause any issues down the line. It is important that we keep track of what lines each line item is ran on so that we can go back and look and/or print a report on it in the future.

After removing the controlsource from the combobox, access still seems to keep track of line numbers on [tblFloorRunDetails]. Before I mark this thread as [SOLVED] I would like to understand why. Is it because of the relationship between [tblFloorRun] and [tblFloorRunDetails]?
 

Users who are viewing this thread

Back
Top Bottom