Dear Lina:
We have produced such forms several times. To give you some idea, the
variable number of City columns will have to be handled using indexing
of the column collection. You should use a horizontal scroll bar
control, and program it to move through the set of variable columns
while keeping the Product column static.
There will need to be a temporary table behind the form and complex
update/insert queries to update back to the Products table. You must
also have a separate Products table, with ID_Product and Product_Name
in it. You shouldn't have Product_Name in the junction table.
Finally, if there is any chance this will be used in a multi-user
system, you will need to keep the previous values of all intersections
so you can tell which were changed. Then you will need to check to
see if any other user may have changed what you have changed, given
the previous value, the current value, and the new value. A conflict
resolution must be built.
This can be anywhere from 8 hours work to build (if no multi-user
features are implemented) to about 20 hours with full conflict
resolution. At going rates, it could easily exceed $1000. It would
take much more time and money than that to teach how this is done.
Probably you can tell why no one is likely to volunteer this much.
However, for an expert programmer, the above outline would be enough
to get started.
I guess someone should write a couple of chapers in a book on how to
do this. I haven't seen that done yet.
Tom Ellison
Microsoft Access MVP
Ellison Enterprises - Your One Stop IT Experts