John Colby
jcolby at colbyconsulting.com
Wed Nov 5 19:26:41 CST 2003
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. John W. Colby www.colbyconsulting.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Jim Lawrence (AccessD) Sent: Wednesday, November 05, 2003 8:05 PM To: Access Developers discussion and problem solving Subject: RE: [AccessD] OT: Corrupted database Hi Rocky: Now that you have mentioned a possible network connection I have ran across a couple of similar incidents over a few years. The problems were always, with 'bound' FEs, spawned by a flaky network card, in one situation and a enthusiastic network tech who had the server auto-reboot over-night with no open-file checking, in another. I just kept trying to open the DBs and finally both did and then I immediately saved everything to a new/clean db. Save all in one case and only lost two weeks of data in the other. I have never used a bound application, with over five users since. That is a good rule of thumb but some developers state the cut-off can be as high as ten users. I know of a programmer who has had limited success hacking out lost data and code with an assembler but I imagine the cost would be prohibitive unless there is absolutely no backup. Jim -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Rocky Smolin - Beach Access Software Sent: Wednesday, November 05, 2003 9:21 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] OT: Corrupted database Don't know. I think it's more likely a network problem or, as the error message says, an abnormal termination leaving the db open. Rocky ----- Original Message ----- From: "Charlotte Foust" <cfoust at infostatsystems.com> To: "Access Developers discussion and problem solving" <accessd at databaseadvisors.com> Sent: Wednesday, November 05, 2003 8:25 AM Subject: RE: [AccessD] OT: Corrupted database > Is it possible one of your users opened the database in Word? That will > certainly cause the situation you've described, and in that case the > database is well and truly hosed beyond recovery. > > Charlotte Foust > > -----Original Message----- > From: Rocky Smolin - Beach Access Software [mailto:bchacc at san.rr.com] > Sent: Wednesday, November 05, 2003 8:14 AM > To: Access Developers discussion and problem solving > Subject: Re: [AccessD] OT: Corrupted database > > > I don't get an error message. It just ponders for about a minute then > Access terminates with no error message and I get to send a message to > Microsoft if I want to (like dropping rocks into a deep pool). > > Rocky > > ----- Original Message ----- > From: "Greg Smith" <weeden1949 at hotmail.com> > To: "Access Developers discussion and problem solving" > <accessd at databaseadvisors.com> > Sent: Wednesday, November 05, 2003 8:05 AM > Subject: Re: [AccessD] OT: Corrupted database > > > > Rocky: > > > > What kind of error do you get when you try to 'repair' the db? The > > following MS article told me the unfortunate news when I was getting > > this type of error on a customer's db. They had to restore from a > > backup copy > I > > had (their tape backup wasn't working...go figure) and reenter all the > data > > since I'd made my copy. > > > > Look at: KB158933 ACC: Error Message: <Database Name> Isn't an Index > > in This Table > > > > If you're getting THAT one, you're hosed. > > > > Greg Smith > > ----- Original Message ----- > > From: "Rocky Smolin - Beach Access Software" <bchacc at san.rr.com> > > To: <AccessD at databaseadvisors.com> > > Sent: Tuesday, November 04, 2003 3:54 PM > > Subject: [AccessD] OT: Corrupted database > > > > > > Dear List: > > > > I have a database from a client which seems pretty well hosed (A2K). > > When you start it you get the message "Database (database name) needs > > to be repaired or isn;t a database". I say go ahead and let Access > > try to > repair > > it but it ends in an abnormal termination of access. > > > > I've tried decompile, jetcomp.exe, and jetutils. No dice. Can't do > > an import into a fresh database either. > > > > I'm out of tricks. Are there any other approaches? > > > > TIA, > > > > Rocky Smolin > > Beach Access Software _______________________________________________ > > 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 _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com