I have a database that tracks all of the insurance claim files that my
department works on.  I have been asked to create a similar database for the
hurricane insurance claim files that our catastrophe team is working on.  

Originally, I had thought just to use the original database and create a
special report that would identify the catastrophe files, but there is no way
that one user can keep the database updated.  The answer then became to
create a second database and allow people outside of our department (temps)
to enter their claim file information into (so that they don't unknowingly
screw up our department database).  I was then hoping that I would be able to
import the information from the second database into the original database so
that our records would be complete.  However, I think we will wind up with
duplicate records every time I merge the two databases.

So here's the question:  There has to be an easier way to allow multiple
people to access and update and change and add records without screwing up or
jepordizing the integrity of the original database.  

Someone suggested putting the form on the web and letting them enter/change
the information online but not have any direct access to the database itself.
If I split the original database into FE/BE pieces, will this accomplish the
same thing?

Any thoughts that you have would be greatly appreciated.  I'm terrified that
someone is going to corrupt the original database or delete some record by
accident and I'll never be able to know if my data is still completely intact.

Thanks!

Carley