[AccessD] End of an era

[Rocky Smolin]

It’s unusual, IME, for a company to be looking ahead like that. Sounds like
a good place to work. And a full rewrite like Gustav suggests might be job
security.

I couldn’t do it now - take too long to learn C#. I know Access isn’t the
most “robust” front end. All my customers are smaller businesses and Access
FE/BE works well.

What problems were you running into with the current system? Transactions
hosing the back end?

R

On Tue, Mar 26, 2024 at 4:54 PM Paul Wolstenholme <
Paul.W at industrialcontrol.co.nz> wrote:

> Rocky,
>
> The frog in the hot water didn't think it was broke either.  A stitch in
> time...
>
> This app is used by a factory operating 24/7 (and deemed 'essential'
> throughout covid lockdowns) so ongoing support is essential.  Access simply
> wasn't reliable enough for this task without SQL Server.  Even with it we
> operate in fear of the next Microsoft update breaking Access again.
> Pushing the data into a 'cloud' is also not an option for a factory located
> on the outskirts of a rural town - we wouldn't want to be reliant on one
> internet connection to that extent.  An additional issue is the
> performance speed on some forms and reports - especially for remote users
> (workarounds include ADODB forms or investing in remote clients that
> connect to local servers running Access).
> Access developers are thin on the ground and I am officially a pensioner
> already.  I've managed to find a full time Access developer interested in
> taking over from me so that might be the best option (and the reason I
> haven't leapt out of the water yet).
>
> The international owners of this plant could decide to use remote
> developers and different technologies.  That would be a shame.  The plant
> has worked very well with a database system that continues to be customised
> locally to meet local needs by someone who understands local priorities.
>
> Paul Wolstenholme
>
>
> On Wed, 27 Mar 2024 at 10:22, Rocky Smolin <rockysmolin2 at gmail.com> wrote:
>
> > I'd say 'If it ain't broke...' but I think the logical path is probably a
> > web app with the database in the cloud.
> >
> > What problem is the app running into that there's talk about migration?
> >
> > r
> >
> > On Tue, Mar 26, 2024 at 1:55 PM Paul Wolstenholme <
> > Paul.W at industrialcontrol.co.nz> wrote:
> >
> > > Is there a preferred migration path for a multi-user system having a
> > 100MB
> > > Access FE application and a SQL Server BE?  I've been pondering that
> one
> > > for about a decade already (the app is ~22 years old with about 15
> > users).
> > >
> > > Paul Wolstenholme
> > >
> > >
> > > On Wed, 27 Mar 2024 at 07:18, Rocky Smolin <rockysmolin2 at gmail.com>
> > wrote:
> > >
> > > > I'm still doing Access dev, but only a few hours a week for legacy
> > > clients.
> > > > My skills became obsolete just as I was sliding into retirement.
> Timing
> > > is
> > > > everything...
> > > >
> > > > r
> > > >
> > > > On Sat, Mar 23, 2024 at 3:35 PM Ryan Wehler <wrwehler at gmail.com>
> > wrote:
> > > >
> > > > > Company I work for sold. Acquiring company has their own FE/DB
> > solution
> > > > > that is C#/PostgreSQL.
> > > > >
> > > > > Naturally some skills might carry over, but 20+ years of writing
> > T-SQL
> > > > and
> > > > > Access is coming to an end.   Heck I'm not even sure at this point
> if
> > > > I'll
> > > > > be in any developmental role. So far it seems like I'll land in the
> > IT
> > > > > team, but maybe more in a Sysadmin role.
> > > > >
> > > > > Time will tell...
> > > > > --
> > > > > 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
> > >
> > --
> > 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
>