I create ad-hoc databases using MS Access 2000 where users enter their information via forms and view different reports. My Access database is linked to Progress tables using ODBC. I began to have needs for databases I could place on the share drive for users in the organization to utilize at the same time. I knew SQL Server might help with this issue, so we purchased one.
Now, I'm trying to figure out the best way to utilize my new SQL Server with Progress with MS Access as a front-end. I may have made a mistake by purchasing the SQL Server. I thought I could just link the Progress tables to the SQL Server (like in Access), and migrate my MS Access database using MS Access Data Project and it would all work.
Can someone explain to me how I can use my MS Access as a front-end and have the SQL Server or Progress run all the queries, macros and modules in the back-ground with the least amount of migration/learning curve on my side?
Now, I'm trying to figure out the best way to utilize my new SQL Server with Progress with MS Access as a front-end. I may have made a mistake by purchasing the SQL Server. I thought I could just link the Progress tables to the SQL Server (like in Access), and migrate my MS Access database using MS Access Data Project and it would all work.
Can someone explain to me how I can use my MS Access as a front-end and have the SQL Server or Progress run all the queries, macros and modules in the back-ground with the least amount of migration/learning curve on my side?