The Artima Developer Community
Sponsored Link

Design Forum
how to handle migration of messing database design ( MS Access )

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
Kit Chu

Posts: 1
Nickname: kitsnews
Registered: Nov, 2007

how to handle migration of messing database design ( MS Access ) Posted: Nov 16, 2007 12:47 AM
Reply to this message Reply
Advertisement
I have just joined a company and my role is to upsize the current MS Access database to SQL 2K or 2005.

But I found that the database design of the access is really messing and the guy who developed it is fired already.

It is separated into more than 10 mdb file with link to each other to serve different purpose of business function, such as, 1) CRUD of client, 2) CRUD of client's project, 3) CRUD of project team and member, 4) CRUD of resource allocated to different project... etc.

Could anyone suggest some documentation tools which could document the 1)link of access file 2)purpose of each form in each access 3)meaning of field of each table/query ?

Thanks for answering,

Topic: Require help with a test run of a questionnaire Previous Topic   Next Topic Topic: Writing contest for Designers

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use