One of the things about Access, that you will discover if you haven't already, is that the recommended practice is to load the front-end Access file on the workstation, rather than trying to run multiple people in a single copy of the front-end on the server. So that adds another issue to the deployment process. There are several solutions, including a batch file to simply download the .mdb/accdb file each time the database is started. A more sophisticated product is available from FMS inc. or you can roll your own like we have.

Another issue you are likely to encounter is that if you want to have users connecting to the Dev and Test environments, each workstation will need an ODBC driver for each back-end. Once those are setup, they usually don't require any maintenance - until somebody gets a new workstation, or you get a new user. Where are you in the development process - still testing, or do you have users in the production environment? 20 years of experience with this environment has shown that you will probably make 5 or 10 changes to the front-end for every change you make in the SQL Server back-end.