MS Access 2003 - Help understand the structure of mdb, mde and be

Question

I just wanted some explanation as to what happens when you split your tables into the back file and set mde out to use.

When a user accesses mde, is mdb required to go to tabs (or to work)? Let's say I put these access applications on a shared drive for users. If I split the end onto a shared drive and placed mde on a shared drive, should I have mdb for this version of mde to work (communicate with tables)? Or are you talking to mdb who is talking to tables?

Hope this question makes sense.

thanks

EDIT:

One more question: I have MDE installed on a shared network drive, but I was not sure if mdb should be on the same shared drive as mde and back end (tables) .... if not, then I I would prefer not to have it there, because the user insists on getting into it and making copies of it, etc.

But my question is that, as I said, I put MDE on a shared drive, which means that there are about 10-12 people, the maximum, proportion and probability that even half of these people will be there at the same time is very unrealistic. But recently I read that I have to have MDE for each person? It's true? What is a good example of spreading one per person? Previously, I only once went with the fact that I was on a joint assessment, and did not know what it was, if in fact this is a bad approach?

Thanks for your help!

Answer 1

No version MDE does not communicate with its original version of MDB. However, you want the MDB to be in a safe place so that you can make design changes there and then create a new version of MDE from the updated MDB.

A stronger case for MDE is the application that you distribute to your users — unless you want them to redesign any database objects. The back end database traditionally contains only tables, relationships, and indexes. You may decide that the back end may remain in MDB format.

Edit : Do not allow your users to open the same application database on the front panel, regardless of whether the external interface is in MDE or MDB format. Sharing the same interface increases the risk of corruption. All of them can still use the same end with links from the front to background tables.

Tony Toues has set the task of providing each user with their own local copy of the front end quite easily. Check it out useful and free! Auto Web Filter utility.

Answer 2

@HansUp did a great job of asking your real questions, but I'm posting an answer here to try and explain what seemed to bother you.

Take a step back and think about how Microsoft Word is deployed and programmed.

• When you install Word 2007 on your computer, you do not share it with other users - each of you installs it on your own PCs.

• When you install it, you are installing the compiled application, not the source code.

• Microsoft supports and supports source code that you do not need to run Word on your PC.

• The source code for Word is similar to the front-end MDB.

• The compiled Word EXE and all its supporting files are similar to front-end MDE.

• As with using the Word application, you don’t share it, but each user has a separate copy.

• As with Word, your users do not need the source code to run the compiled application, so all your users need is an MDE.

• Like Microsoft, you need to take care of your MDB source code so that it does not get corrupted or lost, so you can continue to update it and create new compiled versions for your users.

It is not difficult when you understand the function and role of different parts. This is confusing due to the fact that MS documentation for Access tends not to promote or explain best practices. I can’t understand why this is so after all this time, but it still exists.

You are well on your way to doing things right.