[AccessD] Another Hosed Database

Can you export t

Joe Hecht
Los Angeles CA



-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin
- Beach Access Software
Sent: Monday, November 10, 2003 3:17 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Another Hosed Database


"Maybe they got that message and didn't tell you..."

I suppose that could possibly happen.  :)

Compact didn't help.  I even put it through the decompile even though
there was no code, just a shot in the dark..  no soap.

They were able to print out all of the data entered since their last
backup, and restore that backup and are now going to re-enter the data,
and hopefully they'll be a little more rigorous in the future about
making and verifying backups.

Rocky

----- Original Message ----- 
From: "David McAfee" <DMcAfee at haascnc.com>
To: "'Access Developers discussion and problem solving'"
<accessd at databaseadvisors.com>
Sent: Monday, November 10, 2003 1:38 PM
Subject: RE: [AccessD] Another Hosed Database


> Rocky, can you compact the db? Maybe it has corrupted records. Usually

> if
its bad enough, you will get an error massage stating "you and another
user are attempting to view the same record..." and leave you with an
uncompacted mdb and a new db1.mdb. Maybe they got that message and
didn't tell you when they repaired the mdb?
>
> David
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Rocky Smolin

> - Beach Access Software
> Sent: Monday, November 10, 2003 12:34 PM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Another Hosed Database
>
>
> Charlotte:
>
> Hey - this is the kind of client that pays the rent.  Anyway, it's not

> in the query (which is in the front end) because when I restore an 
> older copy of their BE db the FE works just fine.
>
> Since my first post I have determined that there is a parent record 
> (agreement header) missing in the header table which has 4 child 
> records (agreement details) in the detail table.  FK in those child 
> records points to a non-existent PK in the parent table).
>
> So I think the repair didn't.  But on the surface, the orphan child
records
> alone should not product the result they're getting.  OTOH, it points 
> to other possible problems in the BE.
>
> Rocky
>
> ----- Original Message -----
> From: "Charlotte Foust" <cfoust at infostatsystems.com>
> To: "Access Developers discussion and problem solving"
> <accessd at databaseadvisors.com>
> Sent: Monday, November 10, 2003 12:02 PM
> Subject: RE: [AccessD] Another Hosed Database
>
>
> > Rocky,
> >
> > You've GOT to get some different clients! LOL
> >
> > What version of Access and have you tried building a new query?
> >
> > Charlotte Foust
> >
> > -----Original Message-----
> > From: Rocky Smolin - Beach Access Software 
> > [mailto:bchacc at san.rr.com]
> > Sent: Monday, November 10, 2003 11:50 AM
> > To: AccessD at databaseadvisors.com
> > Subject: [AccessD] Another Hosed Database
> >
> >
> > Dear List:
> >
> > A client of mine has a database which got corrupted.  I told them to

> > open the back end directly and they got the message which said 
> > database appears to be corrupted would you like to attempt repair, 
> > which they did and it appeared to go OK.
> >
> > However, apparently all is not well, because when I try to add a 
> > record to a detail file - bound form, subform on a tab - the command

> > DoCmd.GoToRecord ,,acNewRec blows up with 'Can't go to specified 
> > record'.
> >
> > When I run the query that is the record source for the subform, it 
> > does indeed not allow additions.
> >
> > When I do the same thing on an older copy of their database 
> > everything works OK.  So I know it's not in the front end.
> >
> > Can this db be saved?
> >
> > MTIA,
> >
> > Rocky Smolin
> > Beach Access Software
> >
> > P.S. Yes they have a backup but no it's not recent.  Apparently the 
> > person responsible for backup up...didn't. 
> > _______________________________________________
> > 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