Martin Reid
mwp.reid at qub.ac.uk
Tue Dec 14 09:38:05 CST 2010
Look at 2010 with Access Services. But the cost for a commercial license could be very high. http://channel9.msdn.com/shows/Access/Microsoft-Access-2010-Demo/ haven't used this feature either but did see some nice video of it at MS. Be much cheaper to go Drew's route and put the mdb on the web server and do some .net code. Martin -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Drew Wutka Sent: 14 December 2010 15:28 To: Access Developers discussion and problem solving Subject: Re: [AccessD] Preparing Database for Web Not really. My admin experience with sharepoint is rather limited. My user experience with it is not very satisfactory. Drew -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of David Emerson Sent: Tuesday, December 14, 2010 1:09 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Preparing Database for Web The company IT guy suggested using sharepoint and putting the whole database on the server. He indicated that then we wouldn't need any web interface. There would only be about 25 staff that would be using it (and it is not high usage) but they are spreads across a couple of countries (well NZ and the West Island sometimes called Australia :-)) Any comments with this approach? David At 14/12/2010, Drew Wutka wrote: >Access is more than capable of running as a backend to a web >application... IF you put the .mdb on the web server itself. When done >that way, it'll run as fast or faster than a SQL Server, and will never >have corruption issues. (Unless you also access it with Access from >across a network, then corruption may still occur). > >I have lots of web based systems that use an Access .mdb for the back >end. > >Drew > >-----Original Message----- >From: accessd-bounces at databaseadvisors.com >[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of David Emerson >Sent: Sunday, December 12, 2010 2: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 The information contained in this transmission is intended only for the person or entity to which it is addressed and may contain II-VI Proprietary and/or II-VI Business Sensitive material. If you are not the intended recipient, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. You are notified that any review, retransmission, copying, disclosure, dissemination, or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com