I Cannot Open My Front End Access File

[zyousafi]

I tried that and it hasn't worked as well I am sorry for the delayed response but I was on vacation and this took a backseat to eating a lot of exotic food and taking pictures with the family

I am thinking in the amount of time I have spent trying to get this issue fixed I could have perhaps developed the same application again.

 

[GinaWhipp]

You could just build another database if you like but the database should open by holdinh down the Shift and then go to the VB Editor and enter the password. I know I asked earlier but I don't see an answer... do you know the password to the VB Editor?

 

[zyousafi]

Yes I know the password but the problem is that the database does not open when I hold down the SHIFT key - I am never able to make it to the VB Editor. That has been the whole problem.

 

[GinaWhipp]

Do you hold down the Shift Key from the time you double-click till the time it is opened? If that doesn't work please see Bob's post (#19) he has offered a solution to get it open.

 

[zyousafi]

Hi Gina! Yes I tried holding down the Shift Key from the time I double-click the file until the time the file is completely open; however I am having no luck. I reviewed Bob's other solution as well; however I have not deactivated the Shift Key so that technically should not apply.

 

[boblarson]

Your post is confusing. If the Shift Key Bypass has not been disabled, then you should be able to open it. Can you post a copy of the frontend file here so we can try? (or you can PM me and I can send you an email address where you can send me a copy and not post it here for everyone).

 

[zyousafi]

Hi Bob! Please accept my apologies for the delay in getting back to you; however we have been celebrating Eid-ul-Fitr here in Pakistan. I would be happy to send you the file on your e-mail address. Let me PM you

 

[boblarson]

So you created this? Right now when I open it, it looks like it does some checking to see of something is there in some directory and then if it isn't there, it closes automatically. A place I worked before had something like that. There was a file that had to be in the same location as the database, named correctly, otherwise it would close. Does it have anything like that?

 

[zyousafi]

Yes I created this That's exactly what I am having a hard time understanding. I use MS Access for applications in a network - essentially it is a Contact Center with 200+ employees. This particular application was initially split; however I removed the links via the Linked Table Manager. After that it never opened. I made sure the name of the database was exactly the same; however I am still having no luck. When I run into a file like this - and if the approach above doesn't work, what should I do? I have done this in the past as well - as a test I mean - split a database on a network and then changed the name of the back-end database and then changed it back to see if it would work. I faced the same problem then as well.

 

[roundup]

Hi,

I ran into this problem the same as you did. What a terrible feeling not being able to open my database for 5+ hours, I had spent so much time on it.

This problem seems to pertain to databases with a custom ribbon! The front end is looking for USysRibbons linked in the back end but cannot get it, causing the program to fail.

The answer to this problem seems to be you have to get the front and back end linked just the way they were so you can get back into your front end. I was fortunate enough to remember how to get them linked up just the way they were on the same network setup.

You must move the USysRibbons table from being linked to the backend to just being in the front end. Then you will be able to open your database without the link being made.

Check microsoft support kb 926533, the forum won't let me post the link.

I had been accessing my database for years, and knew if the link was bad I had to get it working again otherwise I could not access the front end but never really thought of the implications. When my server had moved and everything had been changed I easily realized the implications. The link was not easy to remake.