database structure/change advice

[Anika]

I am working on a project where I have 2 warehouses, each with it's own inventory and am trying to create a way to compare the inventory in each. When I get an order, I would like to know if I have the items on hand and which warehouse houses my goods.

At this time I have my small database working very well for just one warehouse and I'm trying to integrate the other. The one constraint is that the 2 warehouses myst have their own tables, which is throwing me off. It would be easy to just import the data to the already existing table, but that is not an option in this scenario.

I could make it an option, if I had to, by including a flag that would itentify each warehouse. Could someone please offer assistance on structuring this addition to my database for best performance and usability?

 

[raskew]

Hi -

Spreading your issues over multiple-threads will not prove beneficial to resolving your problems.

Please post your database, then stick with one thread.

Bob

 

[gemma-the-husky]

you should just have 1 database. Why do you think each warehouse MUST have its own tables?

you then need to add a table/structure "location" to manage the location of the stock - then each transaction needs al ocation indicator to indicate where the product is.

now finding total stock is easy, and you can also split the stock between locations.