MSAccess.exe Program Error / Using CreateForm Function

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

AC2000
It's funny - if I put a breakpoint in the module and try
to find a bad line, it opens fine. Then continues to run
ok, even after the clearing the breakpoint, until I exit
access. After I reopen and try again (without the break)
it crahses.
I'm also using docmd.movesize so the continuos form sizes
with number of records in the datasource qry.
I've looked in the Dr. Watson log and found a "FAULT" line
thats pointing at what may be a "mov" param, but that
stuff is alien to me.
I've tried DoEvents in several places and that doesn't
help either.
Anybody have any ideas or experienced similar dificulties?
 
AC2000
It's funny - if I put a breakpoint in the module and try
to find a bad line, it opens fine. Then continues to run
ok, even after the clearing the breakpoint, until I exit
access. After I reopen and try again (without the break)
it crahses.
I'm also using docmd.movesize so the continuos form sizes
with number of records in the datasource qry.
I've looked in the Dr. Watson log and found a "FAULT" line
thats pointing at what may be a "mov" param, but that
stuff is alien to me.
I've tried DoEvents in several places and that doesn't
help either.
Anybody have any ideas or experienced similar dificulties?
Click to expand...

I suppose it could be a bug of some kind, or there could be an error in
your code. The only way we'd have any hope of figuring it out would be
for you to post the code. Also, if you'd post exactly what you found in
the Dr. Watson log, maybe somebody who knows how to interpret these
things would have a chance. Knowing the exact error message might help,
too.

The fact that it doesn't happen when you step through the code suggests
a timing issue of some kind, or it could be the result of some kind of
corruption in your VB project. Have you tried Compact & Repair? Have
you tried decompiling your database?

What operating system and service level are you running under? And what
service level of Access 2000?
 
Thanks for the response.
Tried adding a 5 second timer to pause routine (is this
proper handling of the timing issue you suggest or is
there a different way to pause execution?), but that only
worked until I closed it. After re-opening it crashed
again.
How do I de-compile?
Compact and repair doesn't work, same effect as closing
and re-opening, and crashing again.
Since I'm working in client / server, would rather strip
out the module to a blank file, then try and reproduce the
results that way. Then I'll post the code.
Running: W2k-SP4, Office Pro SR1 - w/SP3
msaccess.exe = 9.0.6620.
Going to run office update and see what that says.
 
Thanks for the response.
Tried adding a 5 second timer to pause routine (is this
proper handling of the timing issue you suggest or is
there a different way to pause execution?), but that only
worked until I closed it. After re-opening it crashed
again.
How do I de-compile?
Compact and repair doesn't work, same effect as closing
and re-opening, and crashing again.
Since I'm working in client / server, would rather strip
out the module to a blank file, then try and reproduce the
results that way. Then I'll post the code.
Running: W2k-SP4, Office Pro SR1 - w/SP3
msaccess.exe = 9.0.6620.
Going to run office update and see what that says.
Click to expand...

Sorry, I overlooked this message until now. If you're still wondering
how to decompile, here's how:

1. Make a copy of your database to do this to, in case it makes things
worse than they are.

2. Click Start -> Run, and in the "Open" dialog, enter the following
(substituting your path and file name):

msaccess.exe /decompile "C:\Your Path\YourDBCopy.mdb"

3. I can't remember whether you'll see any indication that your database
has been decompiled. Probably not.

4. Compact the database.

5. Compile the database.

6. Compact the database again.

7. See if it made any difference to your problem. If the problem is
fixed, replace the old, bad copy with this repaired copy.
 
Thanks again for the response.
I did this and it worked once. After closing - opening
access, I ran the form that calls CreateForm again and it
wouldn't open. Then tried to open in design view and
received an MSaccess program error.
Tried again with a new copy from the backup and
experienced identical results.
I also ran detect and repair and received an error message
that the installer couldn't update.. \program
files...\VGX.DLL because it's protected.

I think it may either be with docmd, my installation of
access, or (probably) something in my app that's causing
these faults.
Maybe the way I'm handling an error internally. Having the
(public) function in a module and not directly in the
form's code(as private).


I did set a watch -> break when value changes for docmd,
after breaking and hit continue, received MSAccess program
error. Maybe it's not legal to watch docmd?
 
Back
Top