Questions Before Undertaking A Huge Project.

Here is the scenario:

I have a bunch of people with laptops who go on reviews throughout the state and leave reports on site with the facilities they review. They go out in multiple person teams and work together on reviews. Currently, each person types out their own citations in MS Word on their own computer, saves them to a flash drive and then the facilitator compiles them all together and prints out a report. Then the facilitator comes back to the office, provides their support staff a copy of the report, and then the support staff finalizes it and sends out a letter.

Unfortunately, none of our laptops have Internet capability out in the field.

My idea is to have a multi-user split main database that is stored at our main office. This is for the support staff to store all of the reports. Then I propose to have a local copy of the database (much smaller) on each of the laptops.

Here are my questions:
Lets say that 3 people are out on review together. They each have their entry form on their own computer. The form will be sending information to a few different tables. How can they easily export out their results so that the facilitator could easily import them into their database on their computer.

If all of that were to work somehow, how could the facilitator easily export out the review information tables so that the support staff could import them into the main database.

One of the many stumbling blocks I see relates to Primary keys. The main database will have a main table with a PK of 2008.100 for example. While out on review the reviewers will not be able to use the naming conventions of the main database PK. They might use something like the City name and date (Pensacola02222008). Could that PK be automatically switched into the other format upon import?

Let me know ya'lls thoughts. I have been trying to get my head around this for a few days and have not been able to come up with a feasible solution.

Thanks in advance.