What is After Access database? 3

[Mr2006]

I have Access database and everyone wants to move to something different than access. The office is growing and we have abot 30-40 people all over the world. what is the next step. Everyone want to be able to access the database on line. do you have any suggestion for me...

Thanks

 

[genomon]

SQL Server is scalable and upgrades data nicely from Access. There are 100's of others out there though....

When everything is coming your way, you're in the wrong lane.

 

[dhookom]

A couple popular solutions for remote users are:
[li]Intranet based application using SQL Server as a database and ASP, ColdFusion, .net, or other development environment.[/li]
[li]Continue using your Access application (possibly with SQL server) through VPN or terminal services[/li]

Duane MS Access MVP
[green]Ask a great question, get a great answer.[/green] [red]Ask a vague question, get a vague answer.[/red]
[green]Find out how to get great answers faq219-2884.[/green]

 

[Ed2020]

SQL Server is probably going to be the easiest learning curve.

I've also heard good reports of MySQL and Firebird, although I've not used them yet.

Ed Metcalfe.

Please do not feed the trolls.....

 

[genomon]

Caveat: VPN can be excruciatingly slow without a ton of bandwidth.

When everything is coming your way, you're in the wrong lane.

 

[Mr2006]

Thank you for the feedback. I think I am going to SQL server and front end ASP.net

 

[BSman]

You can go to a SQL Server back end and use your current Access applications for the front end, just linking to the tables in SQL rather than an Access back end database. The main thing to remember is that every table that you bring in to SQL Server should have a single column primary key. If the primary key in Access is currently a multi-column value, then in the SQL Server version of the table add an identify (autonumber) column. This makes the linking of tables work better and easier to set up (you don't have to redefine the combination of columns that make up a "primary key"). And every table must have a primary key.

Access works well as the front end and should serve you very effectively until you get through the learning curve for ASP.net. I think that the most desirable result is to end up with a SQL Server back end that uses a browser based front end; however, there can be a number of significant limitations or at least serious learning paths to negotiate before getting the desired results that are easy to do using Access for the application.

Bob