Problems accessing split database backend

[DG2012]

Hi I am using Access 2013 after many moons ago developing databases in Access 97/2003. I am new to the whole concept of digital signatures. I have created my database and then split the front & back end successfully. But when I try to open the backend (to make design changes) I am getting the error 'This file is missing a digital signature and cannot be opened...'. I have tried creating and applying a selfcert from Office 2010 before splitting the database. I have tried making a accde of the front end but it still has the tables. I have searched google & this forum and I cannot anywhere find anyone having the same issues. Please help as I need to be able to edit the backend to be able to deploy the database! Cheers!

[ranman256]

I know nothing of the digital signatures, but as a workaround, did you try:
make an empty db
import, or export the tables to the empty db.
then try connecting to them?

[DG2012]

Hi OK thanks I I have tried the blank database thing and it has worked...phew!! At least i know I have *some* solution now! But it is confusing why the split the database thing doesn't seem to work anymore? I am using Access 2013 locally and not through Office 365 I don't know if that has anything to do with it

[ranman256]

no, acc2013 works great with split db.

[tospig]

I am having the exact same issue and would like to know if there's a solution that doesn't involve creating a blank database, importing the tables, then re-linking the front-end? Doesn't creating the blank database defeat the purpose of having a split .accdc file?

[tospig]

The solution in this thread is similar to that given here tinyurl.com/q63zraw, so it seems this is probably the best way forward.

[NTC]

There is an issue with the split feature of Access 2013 in that it is creating the back end as .accdc rather than .accdb : June7, Ranman & others that lend a lot of advice - take note. This is now known out there but not resolved. It is in fact happening with my own copy of Access 2013.

The good news is the fix is simple; just manually change the file extension to .accdb I have an Office 360 account and have set up dbs with links to it (SharePoint Lists) and sorta/kinda wonder if this might be a cause or contributing factor....but haven't figured it out yet.

One interesting point on all this is that from the FE everything is fine - you can open tables no problem; but if you attempt to open the back end .accdc directly Access won't let you do it due to invalid certificate.

[June7]

I really do not want to migrate to Access 2013!