Making data accessable on the web

[48Highlander]

I have a fairly large system with 50+ forms, etc. The back end is a mdb file. I would like to be able to put the back end on a web server and have my users acess their data over the web.

I have come to the conclusion that the first step would be to redevelop the back end into a SQL server database. I understand the impact of interruped connections over the internet would be minimized with this type of back end. Is this correct?

To convert the back end to SQL server, I have found a tool called SSW Upsizing PRO. My research indicates this is the easiest and safest way to updgrade. Any comments?

Next, please advise if it is possible for my front end mdb to have a connection to a SQL Server database on a web server. Where would I go to find more info?

Finally, what about security? Should my users set up a VPN connection?

I will greatly appreciate any insights.

Bill J

 

[kjv1611]

From the sounds of your questions, what you NEED is to hire someone to do this for you - either on a full-time basis or at least on a contract basis. I'm sure there are consultants out there who would be willing to tackle this entire project for/with you for the right fee.

Otherwise, I'd say you need to definitely take this one step at a time, and ask specific questions for specific issues as they arise.

--

"If to err is human, then I must be some kind of human!" -Me

 

[Niebotel]

Perhaps the solution is to put your data on a microsoft sharepoint. I did so with my application and I'm quit satisfied. But you will have to migrate to .accdb (ACCESS 2007) but that is not very difficult.

 

[JoeAtWork]

The Upsizing Wizard built into Access does a pretty good job of migrating the database to SQL Server.

please advise if it is possible for my front end mdb to have a connection to a SQL Server database on a web server

Web servers and SQL Servers are usually separate machines. In any case, while it is possible to connect to SQL Server over the Internet (assuming you can find a provider who will allow such a connection), its not a good idea. It will be way too slow. Besides, isn't the plan to make a web application to be the front end to your application? Why would you still need to connect to the database with Access?

 

[trevorwilliams2]

If your goal is to keep the application in Access then Terminal Services may be your only option.

Terminal Services can be put in application mode, where the only thing the user has is access to your application when they log in.

This would also get rid of any problems you might have with deploying updates.