Hard problem with query

[cheberdy]

I have a hard problem with the following data model: I have a Warehouse entity and a Bin entity. They are connected by a 1 : n relationship. Warehouse has as key attribute a warehouse number and bin has 30 bin numbers, because there are 30 bins, and a warehouse number, which is the foreign key. I would like to achieve the following: When a new warehouse is added with new warehouse number, there should be 30 new entries in a query with the new warehouse number and from 1-30 bin numbers. Is this possible?

 

[theDBguy]

If you don't care that the result is read-only, you can use a cartesian query.

 

[CJ_London]

don't see why not - what have you tried so far?

 

[mike60smart]

I have a hard problem with the following data model: I have a Warehouse entity and a Bin entity. They are connected by a 1 : n relationship. Warehouse has as key attribute a warehouse number and bin has 30 bin numbers, because there are 30 bins, and a warehouse number, which is the foreign key. I would like to achieve the following: When a new warehouse is added with new warehouse number, there should be 30 new entries in a query with the new warehouse number and from 1-30 bin numbers. Is this possible?

Can you upload your database?

 

[Pat Hartman]

Here's a sample database that might help. Pressing the generate button on the form adds the number of rows (bins in your case) to the table. Using the tally table allows you to easily vary the number of rows to add without having to use a VBA loop. Instead, you use an append query.

 

[Galaxiom]

Have a look at how a similar problem can be addressed much more elegantly without the insert queries.

Data input from a query and user

My Access skills are really rusty and have to admit to being embarrassed I cannot figure this out. Here is what I need to do in a form. 1. instructor will run a popup from dependent on the item number and quarter which will bring up a class roster. 2. The input form is based on a table where...

www.access-programmers.co.uk

 

[Pat Hartman]

Normally, I would not recommend adding "empty" records but I think that in the long run, having an actual bin record will make more sense and make other processes easier to model. We're talking about something physical in this case. We're not talking about adding rows for monthly payments that might never happen. When the warehouse is built out, the bins are also built.

If @cheberdy understands the method that adds a bin on the fly, then I don't object to it.