Access on the internet

goodfu

Registered User.
Local time
Today, 08:22
Joined
Dec 23, 2010
Messages
140
Access databases are not considered a totally secure way to store data. Would this be more so or less so if you use an Access database as the backend for a website?
 
The database needs to hived off into a separate directory with limited permissions. The need to secure information depends on what you intend to "put up".

Simon
 
In this case it would be credit card numbers.
 
Dealing with Credit Cards you would also need http Secure for processing and Security Certificates.

Simon
 
But would you say it's a bad idea to do that with Access?
 
I'm sorry to hear that but thanks for your help.
 
Just to be explicit: I'm led to believe that the security of data is primarily centered around securing the web server and avoiding use of certain code that would allow exploits (e.g. SQL Injections) and less to do with physical storage of data. In other words, many web server communicate with database server in relatively unsecured manner because they're physically secured by say, network firewalls.

The real problem with using Access as a data storage for a website is that it isn't really designed to be used as a service and thus may have issues. Since there's free RDBMSes out there to pick from, there's no reason to use Access. Besides, just because you use one of those free RDBMSes, doesn't mean you can't use Access with the same RDBMS - you can if you need a rich front-end for maybe internal use while exposing same data via web for different consumptions.
 
But could you link your Access front end to a SQL Server database on a web host's server?
 
If your web host allows remote connection, yes. Some may require you to use some form of VPN or remote login, but as long you work it out with web host, this'll work much better.
 

Users who are viewing this thread

Back
Top Bottom