Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.
ACCDR in access 2010 not working but ACCDB is fine???
This is interesting. My accdb is working without a problem. When I change my ACCDB to an ACCDE and then to ACCDR I get an error which says "Microsoft Access has stopped working" of course there is no way to debug. When I open my ACCDB I get no errors what so ever. Any ideas?
Who is Participating?
Is this occurring on the same machine (as with DB) or a different machine?
If different, possibly there is a Reference error?
mx
If different, possibly there is a Reference error?
mx
Make sure the app compiles without errors.
Then rename to ACCDR and try it in runtime mode.
If that works, then convert it to a DE and see if that works as it should.
Jim.
Then rename to ACCDR and try it in runtime mode.
If that works, then convert it to a DE and see if that works as it should.
Jim.
RT issues are a bitch to troubleshoot - because you can't 'see' anything. I would appear that ... an unexpected error is occurring some place where you do not have error trapping .. OR - worse - some sort of a Microsoft Bug - wherein it's not really generating an error - just shutting down!
mx
mx
mx said it rather succinctly<g>
Given that it compiles cleanly, I would:
1. Make a backup
2. Try decompile
3. Compile again and retest.
If that fails, create a new DB container and import everything into it, compile, and try again.
If that still fails, then your probably tripping over an Access bug.
At that point, your only option is to find what's causing the problem and then work a round it. You'll need to find the bug by placing msgboxes in the code at various points and narrow down when it dies (ie. starting up a specific form).
Jim.
Given that it compiles cleanly, I would:
1. Make a backup
2. Try decompile
3. Compile again and retest.
If that fails, create a new DB container and import everything into it, compile, and try again.
If that still fails, then your probably tripping over an Access bug.
At that point, your only option is to find what's causing the problem and then work a round it. You'll need to find the bug by placing msgboxes in the code at various points and narrow down when it dies (ie. starting up a specific form).
Jim.
Note too there are certain things you cannot do in the runtime, like open a form/report in design view. If you're doing these things, the error trapping may not work and you'll get the abrupt ending you're experiencing.
See this article:
http://msdn.microsoft.com/en-us/library/office/cc136539(v=office.12).aspx
http://msdn.microsoft.com/en-us/library/office/bb501030(v=office.12).aspx
See this article:
http://msdn.microsoft.com/en-us/library/office/cc136539(v=office.12).aspx
http://msdn.microsoft.com/en-us/library/office/bb501030(v=office.12).aspx
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
All Courses
From novice to tech pro — start learning today.
You can ... start your DB in RunTime mode using the /RunTime switch on the command line. This may ... expose the actual error - not sure, but probably not - since it emulates RT. You will probably have to add some error handling any place you suspect an 'unexpected' error might occur.
mx