Error: Jet database engine stopped ...

G

Guest

I've read all the posts to rpurosky's problem dated 5/30/07 and I'm having a
similar problem. I'm the sole user and I've also tried creating a new
database and importing the tables, forms, queries & reports. Question is if
I need to create a new database, can I copy the tables into Excel, do a copy,
paste special and import them into the new database (as I've tried to import
them into a new database with the same error happening)? Also, is it
possible that my form is corrupt and that I will need to create new forms?
 
P

pietlinden

I've read all the posts to rpurosky's problem dated 5/30/07 and I'm having a
similar problem. I'm the sole user and I've also tried creating a new
database and importing the tables, forms, queries & reports. Question is if
I need to create a new database, can I copy the tables into Excel, do a copy,
paste special and import them into the new database (as I've tried to import
them into a new database with the same error happening)? Also, is it
possible that my form is corrupt and that I will need to create new forms?

It's more likely that your forms are corrupt. If your data were
corrupted, it would be unreadable.
 
L

Larry Daugherty

Do you have error handlers in every procedure - both sub and function?
If you are going to add handlers, I recommend that you get MZ tools
(freebie) and set up a handler that includes the procedure name also
form name if applicable. A recommendation: set up MZ Tools with a
complete setup for procedures that includes the error handler and then
*always* put in error handling.

Try the things below in the order that seems best to you:

Open a module and find Tools | Options and select Break on All errors.
That will cause a break on every error encountered whether handled by
your code or not.

If the error always comes up when you are running the same form then
set a breakpoint or even STOP early in the event stream and try to
narrow things down by the process that best fits your situation. If
re-firing Access works fairly quickly then I'd take note of the entry
to every event or function and then step Through or Around it (I
forget which term). At some point you'll crash. When you restart,
open the code and set a breakpoint at the start of the crashing
procedure. Take careful note of the next line to execute - it might
help to select just the offending procedure and then print just that
selection. That way you can check off each line of code that
successfully executes. Sooner or later, you'll crash! I'd leave this
one until after trying the /decompile suggestion. If the decompile
solves it then the form wasn't the issue. If decompile doesn't fix it
and you are sure it's the form you will still want to know what it was
on the form that caused the problem. That way you can identify the
problem area and change the offending code.

Open your application with the /decompile option. Best done with a
separate icon on your desktop. For each development system I always
have two icons on the desktop for each application under development:
one for normal running, coding and debugging. another for the
/decompile opening. Given the ability to enforce "compile on demand"
you could arguably get away with just the one for /decompile.

There may be a lot of sweat and tedium in resolving your problem but I
think you'll get there using the above. Others will probably chime in
with similar and other suggestions.

I haven't read the post you cited so may have contributed nothing new
at all. :)

HTH
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top