Migrate Access 2007 database to FEBE

I administer an Access 2007 dastabase.  I need to migrate 40 stand alone versions of the database to a single FEBE configuration on a secure server.  

Q: Is there anything I should know before deploying this?  Simulations have gone smoothly...which is what worries me.

Q: Should I consider migrating to Access 2010 while I am making changes?  My company is on Office 2010 so this would keep OAS on the same page.
CLTMARKMANAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

David Johnson, CD, MVPOwnerCommented:
I need to migrate 40 stand alone versions of the database to a single FEBE configuration on a secure server.  

Why would you have 40 stand alone versions of a database and not use a central file/database? How do you plan on syncing these databases?  

What is FEBE? and what is OAS?
0
CLTMARKMANAuthor Commented:
The original vision was a stand alone database, used to record equipment maintenance in 40 different but similar locations throughout the company.  As the vision has evolved we realized we should have everyone working in the same database instead of separate.  (Sounds pretty short sited, but the fundamental intent of the database has changed.)

FEBE is Front End Back End-meaning splitting the database and have all locations linked to the same tables on a secure network server.  OAS is Office Automation System-an acronym I picked from the in-house IT group.

What do you mean Syncing?  Once their data is transferred to the FEBE configuration, what syncing is required?
0
David Johnson, CD, MVPOwnerCommented:
As you configure each machine, you could export each separate database to a csv and then import it into the master database, the problem being that the indexes will try and overwrite each other.. what you could do is prefix each table with the department name/number or machine-name of the originating database

I'd try 2 machines in a test environment first, just copy off their mdb's and this way you can check for problems/errors, don't forget to do a complete test.  If this works out then you can roll it out.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Applications

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.