[AccessD] OT: Corrupted database

Charlotte Foust cfoust at infostatsystems.com
Thu Nov 6 10:49:55 CST 2003


Don't forget flaky users in that list, John! <VBG>

Charlotte Foust

-----Original Message-----
From: John Colby [mailto:jcolby at colbyconsulting.com] 
Sent: Thursday, November 06, 2003 8:34 AM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] OT: Corrupted database


ROTFL.

>I've cleaned up after some and it was NOT pretty!

Amen to THAT.

Being bound / unbound appears to have little to do with anything when it
comes to corruptions.  A corruption occurs when JET attempts to save to
a db and the connection is broken for some reason.  That may be the
computer turned off (power loss / off switch - at the WS OR THE SERVER
OR THE ROUTER), or a flaky NIC, or a flaky cable, or a flaky router.
This will occur whether it is a bound form doing the write or an unbound
form doing the write.  You can have a bound form open and staring at
data and lose power with no ill effects, IF no write is occurring.

Unfortunately these urban legends get started, and then just pick up a
life of their own.

John W. Colby
www.colbyconsulting.com

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Charlotte
Foust
Sent: Thursday, November 06, 2003 11:22 AM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] OT: Corrupted database


I have to chime in on the other side.  I've been building Access apps
using bound forms (yes, JC, I *do* use bound forms ... just not
*always*!) since Access 1.  Anytime I've seen serious corruption, there
has been a darn good reason for it, either between the chair and
keyboard or within the network itself.  I've always built my apps with
multiple users in mind, but I've often heard the same urban legends.  In
fact, the truth depends on how the application is built.

The people who knock Access generally know little about it and how it
works or have never encountered a well-built Access application.
Unfortunately, there are a large number of "practitioners" out there who
call themselves Access developers because  they've managed to build
themselves a database that sort of does what they want.  Their work
tends to give Access development a bad name.   I've cleaned up after
some and it was NOT pretty!

Charlotte Foust

-----Original Message-----
From: Jim Lawrence (AccessD) [mailto:accessd at shaw.ca]
Sent: Wednesday, November 05, 2003 7:32 PM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] OT: Corrupted database


Hi John and Stuart:

Not trying to re-kindle the bound/unbound debate but as most of my
contracts are with the local provincial government and they have a
specific rule. All databases with greater than ten users must be build
on SQL technology. That technology extends to Oracle and sometime MS SQL
and unbound forms. Therefore, I have little opportunity experiment with
Access environments with a large user base. The closest I came to a
significant bound Access database was a private client with just under
twenty users but they moved their server to Linux and subsequently a
MySQL BE.

Maybe all these concerns with larger Access bound form applications, are
part of a local urban legend, or Database companies and DBAs who wish to
promote the myth to their own end but I for one have not had great
memories with a couple of applications. Once burned...twice shy.

My two cents worth
Jim

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Stuart
McLachlan
Sent: Wednesday, November 05, 2003 5:54 PM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] OT: Corrupted database


On 5 Nov 2003 at 20:26, John Colby wrote:

> Jim,
>
> I have a client with ~30 users in the database (bound forms) from 8-5
daily
> and have not had a single corruption in coming up on a year now.
>

Me too!   (For a couple of years now)
<VBG>

Apart from that one, I have several others which regularly have ~10
users in them all day with no sign of corruption yet.








--
Stuart McLachlan
Lexacorp Ltd
Application Development,  IT Consultancy http://www.lexacorp.com.pg

_______________________________________________
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


More information about the AccessD mailing list