Specific Code?

[JayX]

I have created a database that deals with inventory control. My next step that I have been approaching is to click a command button that opens up a separate from but takes specific information from FORM 1 into the new FORM that I just created.



So if a specific Employee takes out 4 aprons from a total of 50 and there are now 46 left, I would like the submit button to transfer that data over accordingly to Inventory control form in the correct text boxes.

Specific Example: If employee John Doe takes 4 aprons from a total of 50 which now leaves 46 how can I transfer that data into the other form showing specific information like 'Product ID' taken, 'Date' it was taken, 'Product Description', 'Employee' who took it, 'Amount Taken' and, 'total' left.

Is there a certain code that does this? Here are screen shots so you can get a visual

Please Help....

[hertfordkc]

However, I think VBA will be required.

[JayX]

What kind of event procedures exactly? And I am not to familiar with VBA anyway you can assist or guide me would be greatly appreciated..

[hertfordkc]

the Onclick event in your first form. That event procedure might simply open the second form.
The second form's OnOpen event could make the first form invisible, if desired, and transfer information from the current record in the main form to the controls in the second form. When finished with the second form, the Onclose event could make visible the first form.
Most of the BBA would be the transfer statements in the form of
Form2![Field1] = Form1![Fieldx]
Form2![Field2] = Form1![Fieldy] ........

[pbaldy]

I personally would not try to store the quantity on hand. It can be difficult to catch every possible way a user can affect the data. I would simply calculate it from transactions. Given your example, you have a transaction recording the receipt of 50 aprons and another transaction recording the taking of 4. It would be a simple query to net those out to 46. There's a discussion of the topic here, though Allen's code is more complicated than many situations require:

http://allenbrowne.com/AppInventory.html

[hertfordkc]

Operating from transactions is simpler within the Access framework, but I have a nagging fear that messing up a transaction will totally trash the inventory calculation. In any case it comes down to garbage in, garbage out.
It is easy to become fixated on forms and forsake good database design. Take Paul's suggestion to heart, and reconsider your design.
It can work either way.