2007 Runtime

[CEH]

Having an odd problem with 2007 runtime. I developed an app some years back, did it in Access 2002. An early one I can tell because I used the "Switchboard" Well, I loaded this on a computer with only Runtime 2007. Crashes everytime I try to start it. Thought it might be the switchboard so replaced that with a form. No luck, still crashes on startup. So on another computer, I converted it to accdb....works fine, then change name to accdr... Again, crashes every time. Any known problems that would cause this behavior?

 

[SOS]

Perhaps there are unhandled errors occuring. That would cause a runtime to crash.

 

[ajetrumpet]

how are you changing the ext's? i have found RT to be a big pain in the butt. doesn't matter what you are doing. and I also know from experience, that runtime errors will cause a message popup that says something like, "application has encountered an error and needs to shutdown". and you don't have a choice after that.

why are you changing it to an "r" ext? what does that change? r u just doing that to avoid user changes to it? if so, you can also do that with a "db" file. shut the bypass keys off, special key specs, turn off shortcut menu options, etc...

 

[SOS]

that runtime errors will cause a message popup that says something like, "application has encountered an error and needs to shutdown". and you don't have a choice after that.

And that is caused by UNHANDLED errors. If you have the correct error handling in place you won't get those.

why are you changing it to an "r" ext? what does that change? r u just doing that to avoid user changes to it? if so, you can also do that with a "db" file. shut the bypass keys off, special key specs, turn off shortcut menu options, etc...

An ACCDR is either an ACCDB or ACCDE with the last letter changed and then it runs in "runtime" mode when you use the full version of Access. So you can emulate runtime situations.

 

[CEH]

OK.... I see you answered the question about accdr....And Yes, I am trying to emulate runtime on the other machine.
Error handling...Well, there were some places in the code with no error handling...loaded the mz tools to make fixing quick...Added to all code... still the same results. No error message, just the box wanting to send report.... Theres nothing that complicated on this db....No lengthy code...only one simple module just to extract user name.......

 

[SOS]

I heard, from MVP Albert D. Kallal, that if you compile to an ACCDE file (also works with MDE files) you won't get runtime crashing if unhandled errors occur.

 

[CEH]

OK......Tried it.. Changed the accde to accdr.... same thing.

 

[ajetrumpet]

And that is caused by UNHANDLED errors. If you have the correct error handling in place you won't get those.

An ACCDR is either an ACCDB or ACCDE with the last letter changed and then it runs in "runtime" mode when you use the full version of Access. So you can emulate runtime situations.

I understand all of this SOS. i think my point was missed. i think he's got it nailed down though, whatever the problem was. good luck with it.

 

[CEH]

Well, tried something that worked...Don't know why...but...
Created a new blank DB in 2007 and imported all objects into it. Now when I change it to accdr it opens and runs.....Unsure of why this worked....but it does. Access.....go figure.......

 

[SOS]

Probably some corruption was occurring.

 

[vbaInet]

Also, it could have been that some legacy code needed to be ported.