Unbound textbox in bound form

[Evilferret]

I'm working on a bound form that looks a bit like this:

| INVENTORY | Inventory item name


| ITEM PHOTO | Inventory item quantity (Unbound)

The idea is that each inventory item in the database will be displayed (Photo and name) but no quantity will be displayed. The user can then input the quantity of each item that was produced on any given day. This is a continuous subform.

What's the best way to approach this? The unbound quantity doesn't seem to work, as typing in the textbox of one detail updates all other details.

There is a 1-to-many relationship between the inventory table and the parts produced table. The quantity resides in Parts Produced while all the other data on this form resides in Inventory.

[Rod]

Where is the control for the quantity? If it's in the body of the continuous subform you have problems.

[Evilferret]

The textbox for the input of the quantity is in the Detail section of the continuous sub-form; This approach does not work.

What approach can you recommend?

Here's a screenshot of the continuous form. As you can see, each part has an image and a name, and a textbox for the quantity produced. I want each textbox to be able to have a separate quantity

Thanks

[Rod]

No, it doesn't, does it! Type in a quantity on one row and all rows inherit the same value.

This is a common requirement and always a tough one to solve. The solution chosen often depends upon volumes and the percentage of updates expected. Let me explain a couple.

1. For large volumes and/or a high percentage of updates - i.e. a real pound-away data entry task - the most appropriate solution is to create a table based on inventory but with an extra column for entry of the quantity produced. At the end of the data entry session this table is scanned and for each quantity entered a new record is added to parts produced. If the data entry is not quite so fast and furious then you could create/update a record on parts produced as you move from row to row on the continuous subform. A variant is to create, not a data entry table, but a whole set of new records on parts produced for this session. Then the quantity field may be bound to its database counterpart. Afterwards delete all zero records.
2. For low volumes and/or low percentage updates then an unbound textbox is placed in the header or footer of the subform, or anywhere on the main form. Quantities produced are entered in this textbox for the current row in the continuous subform. The to-and-fro nature of this solution can be alliviated by introducing up and down command buttons for the continuous list.

Otherwise I can think of no more 'standard' solutions; peculiar situations may however give rise to peculiar solutions.

Anyone else out there got any ideas?

[Rod]

Just seen your pictorial example. Solution 2 is not for you!

[Evilferret]

Thanks for the help Rod. Solution 1 worked great.

Added a bit of VBA to save dirty records to the temp table, then rewrite the data from the temp table to the final table, but nothing too major.