Access BE to SQL Database

[PercyN]

I have an access app I recently started to develop with nicely done FE and BE. My client however is worried that with 10-15 concurrent users generating close to 150 transactions per day will cause the database to start acting funny acting funny after a couple of years. He prefers an SQL database. My questions are:
1. I'm very confortable with using access, how easy is it to attach my FE to an SQL database, is it even possible? Does it involve a straigh forward process I can learn quickly or do I have to go to school all over again?
2. Are there some good tips on how I can accomplish the same task still using an access DB? Maybe using multiple databases (and reserving one DB for only the table with the most trasactional data) etc.

Thanks very much in advance

 

[dhookom]

I typically use SQL Server for my applications. There are a number of resource on the web regarding migrating your data to SQL Server.

Managing tables, views (queries), and other objects on SQL Server is not much more complex than Access. There are security and other functions that must be considered.

Duane
Hook'D on Access
MS Access MVP

 

[dhookom]

I just read a post from Bill Mosca in another forum.

When you upsize your database from Access to SQL be sure to use the SQL Server Migration Assistant for Access. It's much better than the one built into Access. You can download it from

http://www.microsoft.com/en-us/download/details.aspx?id=28763

Bill has great Access resources at his web site.

Duane
Hook'D on Access
MS Access MVP

 

[vbajock]

Get a copy of this:

http://www.amazon.com/From-Access-Server-Russell-Sinclair/dp/1893115240/ref=pd_sim_b_2