Migrating from MDB to SQL
I am in the process of transfering my Access databases to SQL Server 2005 using the 'SQL Server Migration Assistant for Access'. We currently use Access as our front end but since we are moving the back end data to SQL I am looking at using a different 'front-end' solution. I have looked at using ASP, InfoPath, or just staying with Access. Does anyone have any advise? I would like to make the migration and implementation as simple as possible.
ASKER
Deployed to disconnected users, or all on the same network? all on the same network
Used with the save version of Access, same OS? All users using Access 2003 with XP Pro SP2
How many concurrent (i.e. at the same time) users will be using this app? 10-15 concurrent users
Hold any confidential information? no, all users will have full access to all data
Have any real-time processes (stock trading)? no
Have any huge legal liabilities if the process fails? no
What is your companies' existing support skillsets? Microsoft Access with minimal VB scripting
Would you ever need to deploy a modification immediately, or can they wait for a more periodic updating? periodic
Used with the save version of Access, same OS? All users using Access 2003 with XP Pro SP2
How many concurrent (i.e. at the same time) users will be using this app? 10-15 concurrent users
Hold any confidential information? no, all users will have full access to all data
Have any real-time processes (stock trading)? no
Have any huge legal liabilities if the process fails? no
What is your companies' existing support skillsets? Microsoft Access with minimal VB scripting
Would you ever need to deploy a modification immediately, or can they wait for a more periodic updating? periodic
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I personally like InfoPath over Access. If your existing Access front end is acceptable then you can port it like FP says but if you want to make improvements or new front ends then InfoPath has some advantages.
Infopath can make a much nicer looking UI for the user and the out of the box functionality is much greater. It also is much faster to develop and deploy solutions for you. It is easier for knowledge workers to learn so that they can make their own front ends.
Once you get past the learning curve I have greatly preferred it.
Another advantage of SQL will be SQL Reporting.
Infopath can make a much nicer looking UI for the user and the out of the box functionality is much greater. It also is much faster to develop and deploy solutions for you. It is easier for knowledge workers to learn so that they can make their own front ends.
Once you get past the learning curve I have greatly preferred it.
Another advantage of SQL will be SQL Reporting.
Hi,
If you want to move entirely from MS Access or any MS stuff
you could use OpenOffice for your forms.
http://www.openoffice.org/
Cheers,
za-k/
Thanks for the grade. Good luck with your project. -Jim
So far, you haven't told us anything about your business needs, which is what drives a front-end solution decision.
Is/does this app...
Deployed to disconnected users, or all on the same network?
Used with the save version of Access, same OS?
How many concurrent (i.e. at the same time) users will be using this app?
Hold any confidential information?
Have any real-time processes (stock trading)?
Have any huge legal liabilities if the process fails?
What is your companies' existing support skillsets?
Would you ever need to deploy a modification immediately, or can they wait for a more periodic updating?
The answers to these will dictate which front-end to use.