DAO; weird crash of MSAccess

[Robert Waters]

Hello,

I have a whole lot of VBA DAO code in one of my databases; every so
often, Access crashes (and prompts me to backup the db, etc...)
mysteriously when I call a function (it is not the same function every
time, nor is it the same calling method e.g. button/query/manual
call).
The only way that I have found to fix it is to:
1. Enter the VB/macro editor
2. Set a breakpoint _anywhere_ in the function that I want to call
3. Run to that breakpoint and don't resume execution (stop the
function)
At that point, everything works _perfectly_ again!

Has anyone experienced similar behavior?

Thank you,
R Waters

[Allen Browne]

This kind of corruption is not uncommon when you are developing the
application, i.e. modifying the objects and their code.

Decompile a copy of the database by entering something like this at the
command prompt while Access is not running. It is all one line, and include
the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"

You may be able to reduce the frequency of corruption by following the
things in this article:
Preventing Corruption
at:
http://members.iinet.net.au/~allenbrowne/ser-25.html

--
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.

"Robert Waters" <ro******************@gmail.com> wrote in message
news:af**************************@posting.google.c om...

Hello,

I have a whole lot of VBA DAO code in one of my databases; every so
often, Access crashes (and prompts me to backup the db, etc...)
mysteriously when I call a function (it is not the same function every
time, nor is it the same calling method e.g. button/query/manual
call).
The only way that I have found to fix it is to:
1. Enter the VB/macro editor
2. Set a breakpoint _anywhere_ in the function that I want to call
3. Run to that breakpoint and don't resume execution (stop the
function)
At that point, everything works _perfectly_ again!

Has anyone experienced similar behavior?

Thank you,
R Waters

[tombsy]

Hi Rob,

Access is funny sometimes.
I have had experience when a code module can become corrupted and creates
redherrings.
Ths has only happened on 2 occassions over years of developing.
The solution was to create a new module and copy all the code from the old
one and paste into the new one. Delete the old module, recompile, and it
removed the invisible corruption.

This may not fix you prob but worth mentioning here
regs
Tombsy

"Robert Waters" <ro******************@gmail.com> wrote in message
news:af**************************@posting.google.c om...

Hello,

I have a whole lot of VBA DAO code in one of my databases; every so
often, Access crashes (and prompts me to backup the db, etc...)
mysteriously when I call a function (it is not the same function every
time, nor is it the same calling method e.g. button/query/manual
call).
The only way that I have found to fix it is to:
1. Enter the VB/macro editor
2. Set a breakpoint _anywhere_ in the function that I want to call
3. Run to that breakpoint and don't resume execution (stop the
function)
At that point, everything works _perfectly_ again!

Has anyone experienced similar behavior?

Thank you,
R Waters