[AccessD] Access Back End in the Cloud

After being more or less forced by one of my clients to set up a SQL server
BE for an Access FE, I am now a convert.  It's faster and more reliable.
 Setup is fussier, and there is definitely a learning curve, but it sure
works!  Two years, not one corrupt BE.

LinkedIn has an 'MS Access with SQL Server' group, with lots of good tips.

Doug


On Mon, Oct 14, 2013 at 3:35 PM, Rocky Smolin <rockysmolin at bchacc.com>wrote:

> This is for a commercial product (the one I just divested myself of in
> March) aimed at small manufacturers.  So SQL is really to much horse for
> that cart.  And requires a level of expertise to maintain that Access
> finessed for me. So for that kind of app the mdb BE works really well.
>
> r
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Arthur Fuller
> Sent: Monday, October 14, 2013 1:45 PM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Access Back End in the Cloud
>
> I just don't see any point in using an MDB as a back end, and doubly so if
> the BE is in the cloud or on a Terminal Services. SQL Server's free edition
> or MySQL are both far superior choices, and in either case you get the
> additional performance of stored procedures and views.
>
> Arthur
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>