[AccessD] Back from SQL Server

Paul Wolstenholme Paul.W at industrialcontrol.co.nz
Sun Mar 6 22:21:40 CST 2022


Bob,

Paul H's advice is sound.
SQL Server express is free and the data limit is far bigger than it
originally was.  In a multi-user environment it is FAR more robust than
using an Access back-end.  Access back-ends always used to get corrupted
from time to time.  Moving from SQL Server to SQL Server express is
probably trivial.

Paul Wolstenholme


On Mon, 7 Mar 2022 at 17:14, Paul Hartland via AccessD <
accessd at databaseadvisors.com> wrote:

> Is it cost driving the decision back to access, can they not go to SQL
> Server Exoress ?
>
> On Mon, 7 Mar 2022, 04:10 Stuart McLachlan, <stuart at lexacorp.com.pg>
> wrote:
>
> > What sort of connection to the SQL Server (what driver?)
> >
> >
> > On 6 Mar 2022 at 19:46, accesspro at cox.net wrote:
> >
> > > Hello to the list,
> > >
> > > A long time ago I did a pretty complex Access app.
> > > The client went on later to have someone hook it up to SQL Server.
> > > They now are scaling their biz back and wish to just use Access. I bet
> > > there is a way to "import" the tables back into Access, but I don't
> > > know how. Not too concerned about any views yet.
> > >
> > > TIA
> > > Bob Heygood
> > >
> > > --
> > > AccessD mailing list
> > > AccessD at databaseadvisors.com
> > > https://databaseadvisors.com/mailman/listinfo/accessd
> > > Website: http://www.databaseadvisors.com
> > >
> >
> >
> > --
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > https://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
> >
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>


More information about the AccessD mailing list