I had been just wanting some explanation regarding what's going on after you have split your tables out right into a back finish file, and hang an mde out to be used.

Whenever a user accesses the mde, may be the mdb still needed to get at the tabes (or to be able to have great results)? Let say I put these access applications on the shared drive for those to make use of. Basically split the be finish onto the shared drive, and placed the mde around the shared drive, would I the mdb need to exist for your version mde to operate (talk to the tables)? Or does the mde kind of talk to the mdb which talks towards the tables?

Hope this is sensible.



One additional question: I've an MDE set on a network share drive, but I wasn't certain whether or otherwise I needed to possess the mdb present on a single share drive as my mde and back finish (tables)....otherwise i quickly would rather not have access to it there because user insist upon engaging in it, and making copies from it and the like.....

But my real question is, when i stated I put A MDE on a shared drive, meaning there's one which about 10-12 people max, share, and also the likelihood that even half these individuals could be inside simultaneously is extremely very impractical. However I lately read which i must have an MDE for each individual? Is the fact that true? What is a great one of disbursing someone to each individual? I've only ever gone using the one on the shared appraoch before, and was not aware this was, if and it's also, a poor approach?

Interesting help!

No the MDE version doesn't maintain any communication using its original MDB source version. However you need to keep your MDB inside a rut so that you can make design changes there, after which produce a latest version from the MDE in the up-to-date MDB.

The more powerful situation to have an MDE is perfect for the front-end application you distribute for your customers --- presuming you don't would like them altering the style of any database objects. The rear finish database typically consists of only tables, associations, and indexes. You might decide the rear finish usually stays in MDB format.

Edit: Don't let your customers to spread out exactly the same front-end application database, no matter if the front-end is within MDE or MDB format. Discussing exactly the same front-end increases the chance of corruption. They are able to all still share exactly the same back finish with links in the front-end towards the back finish tables.

Tony Toews makes the task of giving each user their very own local copy from the front-end simple enough. See his helpful and free! utility at Auto FE Updater.

@HansUp has been doing an excellent job of responding to your actual questions, but I am posting a solution here just to try and explain what appears to possess confused you.

Take a step back as it were and consider how Ms Word is used and designed.

  • Whenever you install Word 2007 in your computer, you do not share it with other customers -- you both installs it by yourself Computers.

  • Whenever you do the installation, you are setting up the put together application, not the origin code.

  • Microsoft keeps and keeps the source code, which you don't have to run Word on your computer.

  • The origin code for Word is much like the front-finish MDB.

  • The put together Word EXE and every one of its supporting files is much like the front-finish MDE.

  • Just like the term application files, you do not share it, but give each user a person copy from it.

  • Just like Word, your customers have no need for the origin code to operate the put together application, so that all your customers need may be the MDE.

  • Much like Microsoft, you have to take proper care of your source code MDB to ensure that it does not get corrupted or lost, in order that you could still update it and convey new put together versions for the customers.

It isn't complicated whenever you comprehend the function and role from the various parts. It's confusing due to the truth that MS's documentation for Access tends to not promote or explain guidelines. I can not quite realise why this is actually the situation in the end this time around, but situation.

You are well in order to doing things correctly, though.