Identical DB's needing reporting in one

[Carri]

Hi, I'm really stuck

I have two identical DB's each being used by separate tour offices both on the same server.

One of the offices books all the tours for both offices.

How can I get all the tour requests to appear in one layout and still be able to communicate though the records (leave notes for the other office etc. - information changes often).

For example if we're booking tours to the zoo. 4 could be though office 1 and 2 could be through office 2. All 6 need to be viewed on the same layout to book together as well as always be able to check availability etc.

I don't know how to set up the relationships or the layout, any suggestions would be most welcome.

They don't want everyone on the same DB - it's more complicated. Thanks

[Josh Ormond]

It's not the best setup...but probably would need to import the records into a single file (possibly a 3rd file), with a field indicating which office it came from.

Then you could do what you need. Again, not a good way to handle the scenario (you really should get it setup into a single solution, and segregate the data by using a field to distinguish data of one office from the other).