By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,956 Members | 1,657 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,956 IT Pros & Developers. It's quick & easy.

A97 Corruption

P: n/a
Running AC97 under Win2k I have a large database, the front end is
about 32MB and contains literally hundreds of queries, form, modules
etc

Every so often while working on it, say, editing a form, or creating a
module, I suddenly get that horrible 'Program Error' message - you
know the one: 'MSACCESS.exe has generated errors and will be closed by
Windows .....etc

At this point I have no option but to ditch the version I'm working on
because once its corrupted, it's corrupted for good. Or at least thats
what I think to be the case.

So I rebuild a new database from what I believe to be a previous good
one. Then I check that within modules I can do a debug and save all,
and also that I can successfully compact the database.

If all is well I carry on. Then it happens again - that dreaded error
message. It can be after a few minutes, ot it can be OK for a while.

It's driving me mad, so if anybody can throw any light on this I would
be really appreciative - I really would.

Dave
Nov 13 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
Access has always corrupted during heavy development, so if you are
modifying the code, forms, reports, queries, tables, etc (as distinct from
merely editing the data), you can expect it to corrupt regularly.

By following a few guidelines, you can cut this back to only a couple of
times a week in A97, 2000 or 2002. In A2003, it can be cut to once every
couple of weeks.

For suggestions, see:
Preventing Corruption
at:
http://members.iinet.net.au/~allenbrowne/ser-25.html
Some of the items (such as #2 and #3) do not apply to A97, but others such
as #4 and #5 can make a real difference.

HTH
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Dave Griffiths" <da**@k2computers.co.uk> wrote in message
news:56**************************@posting.google.c om...
Running AC97 under Win2k I have a large database, the front end is
about 32MB and contains literally hundreds of queries, form, modules
etc

Every so often while working on it, say, editing a form, or creating a
module, I suddenly get that horrible 'Program Error' message - you
know the one: 'MSACCESS.exe has generated errors and will be closed by
Windows .....etc

At this point I have no option but to ditch the version I'm working on
because once its corrupted, it's corrupted for good. Or at least thats
what I think to be the case.

So I rebuild a new database from what I believe to be a previous good
one. Then I check that within modules I can do a debug and save all,
and also that I can successfully compact the database.

If all is well I carry on. Then it happens again - that dreaded error
message. It can be after a few minutes, ot it can be OK for a while.

It's driving me mad, so if anybody can throw any light on this I would
be really appreciative - I really would.

Dave

Nov 13 '05 #2

P: n/a
Thanks Allen

I had actually found your site thanks to a previous session of
googling.

But here's a strange thing - the development versions of my work all
reside on a NT4 server and I run the program directly from there.
Today I tried copying the front end onto my workstation desktop and
working on it locally. Guess what - fingers crossed etc - no
corruption all day, which is a lot for me.

So I'm wodering if the size of the file - about 33 Mb - is creating
some kind of timing issue as it goes back and forth through the
network to the server.

Just clutching at straws here - but currently happy

Dave

"Allen Browne" <Al*********@SeeSig.Invalid> wrote in message news:<41***********************@per-qv1-newsreader-01.iinet.net.au>...
Access has always corrupted during heavy development, so if you are
modifying the code, forms, reports, queries, tables, etc (as distinct from
merely editing the data), you can expect it to corrupt regularly.

By following a few guidelines, you can cut this back to only a couple of
times a week in A97, 2000 or 2002. In A2003, it can be cut to once every
couple of weeks.

For suggestions, see:
Preventing Corruption
at:
http://members.iinet.net.au/~allenbrowne/ser-25.html
Some of the items (such as #2 and #3) do not apply to A97, but others such
as #4 and #5 can make a real difference.

HTH
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Dave Griffiths" <da**@k2computers.co.uk> wrote in message
news:56**************************@posting.google.c om...
Running AC97 under Win2k I have a large database, the front end is
about 32MB and contains literally hundreds of queries, form, modules
etc

Every so often while working on it, say, editing a form, or creating a
module, I suddenly get that horrible 'Program Error' message - you
know the one: 'MSACCESS.exe has generated errors and will be closed by
Windows .....etc

At this point I have no option but to ditch the version I'm working on
because once its corrupted, it's corrupted for good. Or at least thats
what I think to be the case.

So I rebuild a new database from what I believe to be a previous good
one. Then I check that within modules I can do a debug and save all,
and also that I can successfully compact the database.

If all is well I carry on. Then it happens again - that dreaded error
message. It can be after a few minutes, ot it can be OK for a while.

It's driving me mad, so if anybody can throw any light on this I would
be really appreciative - I really would.

Dave

Nov 13 '05 #3

P: n/a
da**@k2computers.co.uk (Dave Griffiths) wrote:
But here's a strange thing - the development versions of my work all
reside on a NT4 server and I run the program directly from there.
Today I tried copying the front end onto my workstation desktop and
working on it locally. Guess what - fingers crossed etc - no
corruption all day, which is a lot for me.

So I'm wodering if the size of the file - about 33 Mb - is creating
some kind of timing issue as it goes back and forth through the
network to the server.


I'd agree with your conjecture. I've hardly ever worked on a database that wasn't
local but I can certainly see doing development via a server could be troublesome.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Nov 13 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.