Doug Murphy
dw-murphy at cox.net
Sun Dec 12 18:23:06 CST 2010
We have a site that has been running for years with an Access back end. The web forms are ASP based. I created another ordering site for a customer using SQL Server as the back end. This site has higher traffic and the web forms are based on ASP.NET. It seems that the real question is where will the site be hosted and what will you use for the web interface. If your going the ASP.NET route then SQL server will probably be available. If your going PHP then MySql would probably be the way to go. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of David Emerson Sent: Sunday, December 12, 2010 12:00 PM To: accessd at databaseadvisors.com Subject: [AccessD] Preparing Database for Web Team, I have a customer who want a simple database created which will ultimately be hooked up to a web interface (Order screen for fabric samples, and tracking screen to show status of order). I still need to sit down with them to work out the likely number of records, simultaneous users etc (which I am doing tomorrow). Currently their databases are all Access. Assuming the size of the new database will be well within Access limits, is Access suitably robust for web applications, or should I start off with SQL? I will be getting someone else to do the web side of things but want to make sure that I make it as easy as possible (read cheap) for them. Regards David Emerson Dalyn Software Ltd Wellington, New Zealand -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com