[AccessD] Dropped records...Boatloads of them

[Janet Erbach]

Alright.  Thank you all.  I'll look into the options that I may have with
this particular database - I haven't worked with it at all yet, so have no
idea how the code is structured.  And if it's just a matter of having one
or 2 users set up with a wired connection and UPS I may be able to make
that happen.

On Tue, May 26, 2015 at 4:30 PM, Jim Lawrence <accessd at shaw.ca> wrote:

> Bingo... :-)
>
> Jim
>
> ----- Original Message -----
> From: "Stuart McLachlan" <stuart at lexacorp.com.pg>
> To: "Access Developers discussion and problem solving" <
> accessd at databaseadvisors.com>
> Sent: Tuesday, May 26, 2015 2:13:26 PM
> Subject: Re: [AccessD] Dropped records...Boatloads of them
>
> The only solution other than hardening your network connectivity is to
> change your BE to a
> proper RDBMS Server (SQL Server, MySQL or whatever)  with fault tolerance
> built in.
>
> --
> Stuart
>
>
> On 26 May 2015 at 16:03, Janet Erbach wrote:
>
> > Wow.  So are there any other solutions besides:
> >
> > 1) hardwire the network connections
> > 2) install UPS at each workstation
> >
> > Both of which are due to be scheduled for the 12th of Never...
> >
> > On Tue, May 26, 2015 at 3:48 PM, Stuart McLachlan
> > <stuart at lexacorp.com.pg> wrote:
> >
> > > Yes,  that can happen through a dropped connection when data is
> > > being written.  I've seen uit happen occasionally.
> > >
> > > You get a corrupt index. The data is still there, but Access can't
> > > find it.
> > >
> > >
> > >
> > > On 26 May 2015 at 14:35, Janet Erbach wrote:
> > >
> > > > Hello all -
> > > >
> > > > I've corresponded with you all in the last couple of months about
> > > > records dropping from an access database in a manufacturing
> > > > environment.  About once a week we'd find 1-2 dropped records in a
> > > > tool crib database.   We installed UPS's in the area where this
> > > > was happening and...fingers crossed...so far so good.  No dropped
> > > > records since they went in 3 weeks ago.
> > > >
> > > > Today I learned that a manufacturing scrap database was missing
> > > > records, too.  868,105 records to be exact:  All records from 2014
> > > > and several months worth from 2015.  Thankfully I was able to
> > > > restore them from a shadow copy.
> > > >
> > > > The likelihood of an end-user deleting all that data manually is
> > > > so slim that I don't even consider it a possibility.  Can a noisy
> > > > wireless network environment and/or power brown-outs cause such a
> > > > large chunk of data to go missing like that?
> > > >
> > > > Janet Erbach
> > > > --
> > > > 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
> > >
> > --
> > 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
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>