SSMA for Access Vs ADP (Access Data Project )
Posted on 2009-05-20
I inherited an existing membership database for an association of doctors. The database is comprised of a frontend and backend, both of which are Access 2003 MDBs. I want to update the backend to SQL and redesign/modernize the frontend. The DB is quite large in the number of objects that it contains, as not only does it track membership, but it is also an events DB as the association puts on numerous CE event and meetings throughout the year. I have come to the conclusion that it might be better to start from scratch, and redesign it from the ground up.
I have both Access 2003 and 2007 on my PC which I can use to achieve this.
Question: Should I create both front and back ends as MDBs to the point that I am satisfied all is working well, and then use something like SSMA for Access to migrate to SQL (which I believe creates links from the frontend to sql), start with a mdb frontend and sql backend and work from there, or go the ADP route (which I have no experience with)? Or is the a better solution that I have not listed?