I am getting this regularly whilst develping in access 2003 with a complex
form with over 300 objects and much code.
The issue occurs if/when I forget to save often enough and compact and close
and exit - when it does occur it is fatal - repair does not work - the error
message is erroneous - once it has happened it seems you are dead.
Any ponters on how to avoid this - as it sems more luck than judgment at
present?
Ted

The error usually means the db is corrupt. You could try creating a new
empty db and importing all the objects from the old db. If you can narrow
down the problem to a particular object, sometimes the worst-case fix is
re-creating that object from scratch.

Do you have the db split into separate back-end db (just the tables, with
all relationships defined) and a front-end db (everything except the data-
forms, reports, modules, queries, with links to the backend db tables)? If
not, splitting might help. At least it gets your data out from the risk of
corruption.

Do you have the latest Office 2003 Service Pack installed, and the most
recent Access hotfixes?

"TedC" <(E-Mail Removed)> wrote in message
news:1F83E02B-33F7-456D-B47C-(E-Mail Removed)...
>I am getting this regularly whilst develping in access 2003 with a complex
> form with over 300 objects and much code.
> The issue occurs if/when I forget to save often enough and compact and
> close
> and exit - when it does occur it is fatal - repair does not work - the
> error
> message is erroneous - once it has happened it seems you are dead.
> Any ponters on how to avoid this - as it sems more luck than judgment at
> present?
> Ted

Hi Ted,
have a look at this page on preventing corruption

http://allenbrowne.com/ser-25.html


Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia


"TedC" <(E-Mail Removed)> wrote in message
news:1F83E02B-33F7-456D-B47C-(E-Mail Removed)...
>I am getting this regularly whilst develping in access 2003 with a complex
> form with over 300 objects and much code.
> The issue occurs if/when I forget to save often enough and compact and
> close
> and exit - when it does occur it is fatal - repair does not work - the
> error
> message is erroneous - once it has happened it seems you are dead.
> Any ponters on how to avoid this - as it sems more luck than judgment at
> present?
> Ted