Best way to share a split DB?

[shariq1989]

I designed a database for a company at their local branch and now I live far away from the office so I cant access the DB directly on the company systems. The company will call me from time to time to troubleshoot or change things around. In my opinion the best way to around that was to have the guys share the backend with me on a Google Drive, and I could make whatever changes they want. If they want frontend changes, I'd just send them a modified copy of the frontend. I was wondering if there is a better way to do this? I am not allowed access to their network because of IT regulations at the company. I also found it really hard to work with backend and frontend copies because once they would share the BE and FE. The FE could no longer find the BE and I'd have to create a new database and import the forms and queries from the FE and then the tables from the BE... EVERY TIME. This is starting to ruin the fun of having a split DB in the first place. Any advice would be much appreciated!

[June7]

No need to rebuild db just because it is moved. Reset the table links. This can be done with Linked Table Manager or programmatically. Review http://forums.aspfree.com/microsoft-...ue-323364.html

[shariq1989]

The problem I keep having though, is that the front end cant be opened if it doesnt have access to the BE. It tries to open up but then goes to the new database page as if you just merely clicked open the Access 2013 icon to start the application. So I don't really have access to any of the features within the FE including the Linked Table Manager...

[June7]

The front end is an accdb (not accde)? Hold down the shift key when opening the db. This will override most project settings (such as default open form and autoexec macro).

[shariq1989]

The FE is an accdb but I have heard of the SHIFT method before. Doesn't seem to do anything in this case, unfortunately...

[June7]

Odd. You held the shift key down until file completely opened? Does F11 reveal the navigation pane?

It is possible to programmatically disable the shift key open bypass. Maybe that was done to your db. http://www.access-programmers.co.uk/...ad.php?t=51479

Try importing objects in stages, see if db opens. Eventually should isolate the object that is interfering.

[shariq1989]

Neither SHIFT , nor F11 do anything because the database refuses to open. The shift key is not disabled, the db is my personal db practically under lock and key. It just seems like, whenever the BE is moved, this ends up happening. The second I place the BE where is belongs, the FE opens up fine

[June7]

If you want to provide db I will see what I can do with it. Follow instructions at bottom of my post.

[shariq1989]

The FE is 98 MB so it'll take a while to upload... Whats the cap on here?

[June7]

2mb zip is limit. Upload zip to fileshare site such as box.com and post link to the file.

[shariq1989]

Since I cant open the FE, I cant really remove the logo and such from it but I have deleted a bunch of stuff from a copy of the BE. I'd rather not share the FE and BE with the world. Would it work if I PMed you links to the files on my Google Drive?

[June7]

We can try.

[June7]

Here is what I experienced with your files. I have both Access 2007 and 2010. Your original frontend will not open under either. The backend will open just fine anywhere with either version. I have no problem opening the frontend I built by importing your objects. I can move FE and BE to any computer and any folder and relink the tables and everything works.

I cannot replicate the frontend corruption, and can only suggest there is something peculiar to your environment causing this.

[shariq1989]

So any suggestions? Should I continue with what I did? (Dumping the split-DB design and just using the new database with FE and BE components imported in it)

[June7]

Are you asking if you should go to an all-in-one db design? This is not advisable if db is intended for multiple users.

I have never heard of or experienced the behavior you describe with this db. The FE you provided was definitely corrupted but importing to a new db was successful and everything worked normal afterward. I could then move the files anywhere and simply relink the BE tables and can't replicate the corruption.

If you are able to move the files to different locations on your own computer and relink the tables, then what could be happening in the client environment to corrupt the FE?