J
Jack
Hi Tom.
I tried the following suggestions and they didn't solve
the problem...
I performed the compact and repair option which didn't
help.
We were using Access 2000 with the latest service pack
but what I have tried since is installed (new install)
access 2002 with no service packs and it still doesn't
help solve the problem.
We are using Windows XP with SP1.
The database isn't split into an FE/BE split.
Hope these help
Jack
I tried the following suggestions and they didn't solve
the problem...
I performed the compact and repair option which didn't
help.
We were using Access 2000 with the latest service pack
but what I have tried since is installed (new install)
access 2002 with no service packs and it still doesn't
help solve the problem.
We are using Windows XP with SP1.
The database isn't split into an FE/BE split.
Hope these help
Jack
the object or the database is damaged",-----Original Message-----
Hi Jack,
Here is one possibility:
http://support.microsoft.com/?id=308630
The KB article states "This behavior can occur if either
provide more information for people to bewhere object refers to the report itself. You need to
service pack is installed? See Help > Aboutable to help you.
1) Have you tried compact and repair (Tools > Database Utilities > Compact and repair
database...)?
2) Which version of Access are you using, and what
pack is installed? For Windows 2000 andMicrosoft Access for the answer.
3) Which operating system are you using and what service
(FE/BE), with a copy of the FE installed onXP, you can enter the command:
Start > Run and then type in: winver
4) Is this database split into a Front-end / Backend
shown in this KB article, such as verifyingeach PC?
You might try running through some of the suggestions
with garbage (see the section titledthat the temp folder for this profile is not jam packed