mbd no longer opens in A2007

[Beetle]

OK, I'm a little baffled by this one. I have an app (a2000 version) that will
no longer open in A2007. I sometimes work on this app in A2003 and
sometimes in A2007, depending on what location I'm at. Until the last day
or two it worked fine in both versions. I'm guessing I made some change
while working in A2003 that affected it's ability to open in A2007, but I
can't
figure out what. I've made a few form design changes and some minor code
modifications. It still opens and runs fine in A2000 - 2003.

The strange part is that A2007 will make an attempt to
open the file, creates a .ldb file, but then after a few seconds it just
gives up, the .ldb disappears and it goes back to the standard Access
welcome screen. No error message, no nothin. The file folder is a trusted
location, and other apps in the same folder open with no problem.
Attempting to use the shift key bypass also makes no difference. I even
removed all the startup options / limitations but no luck.

Any Ideas?

 

[boblarson]

Maybe you should open it in one of the other Access versions and then do a
compile to see if there is some bad code somewhere that is causing problems.
--
Bob Larson
Access World Forums Super Moderator
Utter Access VIP
Tutorials at http://www.btabdevelopment.com
If my post was helpful to you, please rate the post.
__________________________________

 

[Beetle]

Well I figured out what the problem was, but I'm still not sure exactly what
caused it. I tried several things, including deleting all of the code in the
app
but nothing worked. Then it occured to me that a couple of weeks ago I
added a method to hide the ribbon in A2007 that I found at the following link;

http://msdn2.microsoft.com/en-us/library/bb258192.aspx

which was working fine in A2007 but that was before the app was split.
I deleted the USysRibbons table and now it opens in 2007. Apparently I
did something wrong when I split the app. I'm *nearly* 100% sure that
I did not accidently select the USysRibbons table during the split, but maybe
I'm wrong. When I get a chance, I'll have to do do some testing to see if
it's something I did wrong (probably) or something else.

However, having said that, I do think that the worst thing that should
happen if there is a problem with the USysRibbons table is that the
ribbon just doesn't get hidden. For the app to become completely
unusable seems like a flaw in the method itself.

Maybe MS should should add a notation to the above link that if something
goes wrong with the USysRibbons table, it has the potential to render your
application completely unusable. Good thing for me that I have several
versions of access available and make regular backups.