Question : MS Access onto a websever

Hi

This is a carry on quesion from http:Q_24947091.html


Perhaps because I don't know how to do this my question wasn't put in the best way.

I have a bunch of MS Access databases on a local computer and I'd love to get them up on an ISP / webserver so you can access them via the internet rather than the local computer.

Unfortunately, some of these databases are huge and took me months to design/write the forms, queries etc in ms access.

I'm looking for the best way I can learn to get these databases online in the shortest amount of time (even if security is not great)

Would I be right in saying I'd have to start from scratch using Access as the back end and use ASP.Net as the front end?

Or is there a way to dump the .mdb on a web server and let it run from there?

I've got lots of time to study and work out how to do this, I would love to be given a touch of guidence so I'm not learning stuff I don't need to for this exercise.

i.e.
Setup/signup to a websever
Learn to get access on the web server
Learn ASP.Net for the front end.

I know that the above is a very basic flow, so if you could help me expand so I can understand what steps I need to take?

(I know this whole thing would be much better on another DB i.e. SQLSever Express, which I've just started to learn, but I need the quickest fix for now.)

Hope this is clearer.

Cheers all.

Answer : MS Access onto a websever

You cannot run your Access application directly from a web-based environment, at least not in this version of Access. 2010 has some web-enabled capabilities, however, and may be suitable for your needs, but I'm not sure when it will be released.

That said, the traditional path for this would be to either (a) convert to a web-based language like ASP.NET or (b) setup a Terminal Server for your remote users. If you have a LOT of users, and don't know who will be using this, then (a) is by far the better approach. Terminal Servers require licensing, which can get fairly expensive, and require a good bit of care and feeding at times. Web-based frontends are often easier to deal with, once they're up and running.

Also, as you mention, SSE is a much better choice for web-based stuff than is Access IF you think you're going to have more than about a dozen users. If you're moving to ASP.NET, then the move to SSE or full SQL Server is a no-brainer, since the .NET environment is very tightly coupled with SQL Server.