if you google on this issue, you'll see that it's been posted many times,
and the answer is always: split your database.
the issue of a split database running slower has also been raised many
times, and the answer is frequently: see Tony Toews' Performance FAQs at
http://www.granite.ab.ca/access/performancefaq.htm
as far as the db goes, you might try opening the database directly from
Access rather than from the icon. or try compacting the database without
opening it (try this on a COPY), and then try opening it from Access. if
neither attempt flys, you could try creating a new db, and importing the
tables from the original db - if that works, try importing the rest of the
objects.
if none of the above works, and you don't have a recent, uncorrupted copy of
the db to fall back on, you might try sending a copy of the db to a recovery
service. a few have been recommended in these newsgroups from time to time,
google the groups to see what you come up with.
hth
> I have built an Access database that is located on a network drive at
> my company. The database is accessed by as many as 7 people at any
[quoted text clipped - 20 lines]
>
> Matt
jahoobob - 22 Jun 2006 21:05 GMT
Even if you haven't kept a copy yourself of the db somewhere, check with your
IT dept and see if there is a "good" copy in the backups. You can usually
get them to load it somwhere for you to check it out before ovrewriting the
"bad" copy.
>if you google on this issue, you'll see that it's been posted many times,
>and the answer is always: split your database.
[quoted text clipped - 19 lines]
>>
>> Matt