[AccessD] Preparing Database for Web

On SharePoint it will be a simple file not a web database unless you are using SharePoint 2010. Access 2010 and Access Services. Then you can convert it to a web database running in SharePoint.
Personally I would not bother with anything complex.

Martin


-----Original Message-----
From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of David Emerson
Sent: 15 December 2010 03:34
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Preparing Database for Web

Thanks Darryl,

That is the conclusion I am coming to with the research (having not actually used sharepoint before at all).  It looks like we are going the .net/asp way.

Regards

David

At 15/12/2010, Darryl Collins wrote:

>The company IT folks seem to love Sharepoint, and it is a great 
>solution for document sharing and some basic database stuff (like 
>multiple users managing lists and process flows and event notification 
>etc), but it is not suitable for a true database app in my experience.
>
>Not sure about A2010 which seems to be better integrated for 
>sharepoint, but I suspect you would have all the same issues of 
>corruption and record locking with multiple users if you merely host 
>the single mdb database on sharepoint with multiple users accessing it.
>
>How is sharepoint going to fix that?  I don't think it can.
>
>cheers
>Darryl.
>
>
>
>-----Original Message-----
>From: accessd-bounces at databaseadvisors.com
>[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of David 
>Emerson
>Sent: Tuesday, 14 December 2010 6:09 PM
>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