[AccessD] Report stopped triggering

Hi Kathyrn:

My prognosis, as you have probably already assumed, is that the particular
database has somehow become corrupted. I would open up the bad db, create
and open a new db and copy and paste the components and code from one to the
other, as the standard repair and compact has failed to work.

I have no more to offer than the standard solutions and...
HTH
Jim

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Kathryn
Bassett
Sent: Sunday, August 03, 2003 9:57 PM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] Report stopped triggering


Linked. Have exactly the same routine going on with Muir63.mbd and that
works find. I compared the properties of the two reports and they are the
same.

To add to the problem, I'm now having to reboot between attempts because
abc.mdb locks with abc.lbd whenever I try to run things.

Kathryn

> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Jim Lawrence
> (AccessD)
> Sent: 03 Aug 2003 9:45:PM
> To: Access Developers discussion and problem solving
> Subject: RE: [AccessD] Report stopped triggering
>
>
> Hi Kathryn:
>
>  First question; are your pictures linked or embedded?
>
> Jim
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Kathryn
> Bassett
> Sent: Sunday, August 03, 2003 8:44 PM
> To: dbAdvisors (AccessD)
> Subject: [AccessD] Report stopped triggering
>
>
> Some of you remember my church database that has pictures. I have a report
> that prints pages with the names and the pictures.
>
> Two problems.
>
> 1) It has worked fine until this morning. I tried to print the report
before
> going to church, and it printed to screen just fine. But when I then
clicked
> to print it to the printer, it calculated everything, then "printed" page
> one except it was blank; then it printed page two just fine.
>
> After church, I had more pictures to add, and did so. Then this evening, I
> wanted to try the report again to see if the blank first page happened
> again, only this time . . .
>
> 2) It won't even print to screen. No *lasting* error message, though
> *something* flashes to quickly to read. But it doesn't come up with any
> debug errors or anything like that. Just nothing...
>
> Obviously, I need to solve problem 2 before I can work on problem 1.
>
> Any ideas?
>
> Oh, I had not changed the report in any way, except I changed the name of
> the report (not the query it's based on).
>
> --
> Kathryn Rhinehart Bassett (Pasadena CA)
> "Genealogy is my bag" "GH is my soap"
> kathryn at bassett.net
> http://bassett.net
>
> _______________________________________________
> 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