Datasheet View Form - New Records Changes All Existing

[tdoolittle]

I'm very confused and even more confused on how to explain this, but here we go!

I have a form that consists of two combo boxes. Each combo box is controlled by a query to limit its choices. When you make a selection from the first combo box, the second combo box populates with the second column from the first combo box. It all works fine and dandy. Now I want this to be in a datasheet view. It allows the user to feel familiar with their existing spreadsheet, they simply hit a dropdown, pick an item name, its serial number autopopulates and they can move on... but not really.

When you go to add a second record on the form, your selection for ColumnA changes the existing ColumnA selection. And I have no clue why. To try to explain more, here is an example of what I would want a quick finished sheet to look like:

SKU	SERIAL
Canon 100mm F2.8 USM MACRO	X0004II9CH
Canon 50mm F1.2L USM EF Lens	X0004II9CR
Canon 50mm F1.4 USM	X0004II9DB
Canon 60mm EF-S F2.8 USM	X0004II9DL
Canon 70-200mm F4L USM	X0004II9DV

Pretty simple, add a product, and then another, and then another. But here's what the same completed sheet would look like made right now:

SKU	SERIAL
Canon 70-200mm F4L USM	X0004II9CH
Canon 70-200mm F4L USM	X0004II9CR
Canon 70-200mm F4L USM	X0004II9DB
Canon 70-200mm F4L USM	X0004II9DL
Canon 70-200mm F4L USM	X0004II9DV

The next product to be selected overrides all the other selections in the column. But notice all the serials stay unique to the original item selected, but the SKU changes to match the new SKU chosen for the new record. I'm not sure what would cause this, the only code I have triggering is an "On Change" event that triggers when you select a SKU. The even being that when you select a SKU, the serial number field autopopulates.

Any ideas as to what might be causing this to happen??

[June7]

Is the SKU combobox bound to field? An unbound control will show the same value for all instances of the control.

If you want to provide db for analysis, follow instructions at bottom of my post. Identify objects involved.

[Missinglinq]

As June7 suggested, the Control that holds the data for the SKU Field must be Unbound, in order for this behavior to occur. In order for the Field to be Record-appropriate, it must be Bound to a Field in the underlying Table/Query.

While you look at the Form and see X number of SKU Controls, there is, in reality, only one SKU Control! What you are seeing are multiple instances of that single Control. To fix this, in Form Design View:

• Select the Combobox
• Go to Properties - Data
• In the Control Source Property select the Field in your underlying RecordSource that will hold the SKU selection

Linq ;0)>

[tdoolittle]

Sorry for my late reply, but vacation came early this year! It was Unbound... totally my fault, and now fixed and running! Thank you both!

[Missinglinq]

Glad we could help!

Good luck with your project!

Linq ;0)>