Sharing MDE files

[Chegu Tom]

I have my data base broken into a FrontEnd with forms and reports and a
BackEnd with data. and shared on a LAN

I have some users running Access 2000 and some using Access 2002.

Both kinds of users (access 2000 and 2002) are able to use the .MDE file
made with 2000

They seem to be able to share that MDE file with no problem (2 or 3 users at
a time so far).
There is still enough change and development going on to make it
inconvenient to keep and update MDE files at each workstation.

Is theere any downside of sharing the MDE files that I should be aware of?
If do this for the whole system there may be 5 - 10 simultaneaus users at
some times

Thanks. for any warnings or encouragement

Tom

 

[Albert D. Kallal]

Is theere any downside of sharing the MDE files that I should be aware of?

If do this for the whole system there may be 5 - 10 simultaneaus users at
some times

Well, how have you installed all other software on your system for the least
25 years?

It is simply less reliable, and you are dragging the mde over the network.
So, if you don't care about reliability, and want less performance, then
sure..there is nothing wrong with your setup.

I explain WHY YOU split here (not just tell you..but explain WHY). After you
read this, then answer my first question?

http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm

 

[Chegu Tom]

Thank you for your informative sarcasm. You must be a teacher (that was
sarcasm too.)

So there is no danger of database corruption! If I am prepared to put up
with the decreased performance.

I look forward to your reply

Thanks

 

[Douglas J. Steele]

Actually, I believe there is an increased risk of corruption with sharing of
front-ends. (that's likely what Albert was referring to when he mentioned
reliability)

Why wouldn't you want to use the standard recommendation of each user having
a copy of the front-end on his/her hard drive?

 

[Chegu Tom]

Most users have local front-end files.

I have small groups of users is in offices in the shops that I don't have
ready access to to update the front-end files. The front end changes every
few weeks with requests of new/modified forms and reports as well as
implementation of new ideas and bug fixes. For those inaccessable users I
have been sharing the front-end from the server. Doing that with the MDB
meant occasional corruption of the front end MDB (which I would replace from
a handy backup). The MDE option seems to be working better for them but I
wonder if that opens me up to other problems specific to MDE files. Those
users don't use the database very often or as intensely as the ones in the
office that have local copies of the MDE front end. They usually just look
up the status of things being entered and managed in the office machines.

I guess I should put the MDE files in shared folders on those users disks
and then I can drop new versions in when things change. I can't depend on
them to do any kind of updating on their own and the inaccessability of
their offices is a problem

While I have your attention. I have a question on compiling the Front End.

My computer is using Access 2002, many of the users use Access 2000. MDE
files generated from my access2002 machine will not run on the machines with
access2000. I have been going to the secretary's computer with Access2000
to make the MDE files for acces2000. Is there any way I can make an
access2000 compatible MDE from my Access2002 machine? Then again the
secretary's office isn't that far away.


Thanks for your time

Tom


---------------------------------------------------------------------------------------------------

 

[Albert D. Kallal]

So there is no danger of database corruption!

No, I just finished telling you that there is a increased danger, and
reduction in reliability if you allow users into the same program at the
same time.

If I am prepared to put up with the decreased performance.

The problem as I explained means that one persons problem can then become
the problem everyone else (you did read that article of mine..did you not?).
I guess this is really a issue of how reliable you want things to be, and
how much you care about your work.

I mean, there was a time when doctors used to smoke cigarettes DURING
operations. they would laugh, and say...germs in the air...I can't see
them!!

So, it really is choice of you waking up in the morning and going:

a) I choose to do a good job, and make things more reliable
or
b) I choose to do a bad job, and make things less reliable.

It is really question of your commitment to excellence, and pride in your
work. Some people don't value those things, and I not here to convince you
otherwise....

As I said, if you look around at most software in your office, you have for
years installed that software on each computer, and why break with this
tradition now? What is the so tragic event in your life that makes you wish
to break with how all other software in your office is now installed?

As for the effort to update each pc, you can in less a then a few hours of
your time roll some code to deal with this issue, or simply grab a nice free
updater that Tony has here:

http://www.granite.ab.ca/access/autofe.htm

 

[Albert D. Kallal]

I have been going to the secretary's computer with Access2000 to make the

MDE files for acces2000. Is there any way I can make an access2000
compatible MDE from my Access2002 machine? Then again the secretary's
office isn't that far away.

No, you have to use the same version. In addition, I STRONGLY suggest that
you do a de-compile of the application BEFORE
you compile to the mde. I been deploying a number of a2000 mde's created
from a2003 mdb's,, and they been a source of pain
until I started de-compiling the mdb before making the mde.....

You can read/learn about de-compile here:

http://www.mvps.org/access/bugs/bugs0008.htm

and, you can find her a reg edit that adds the de-compile to the right
click menu for windows:

http://www.mvps.org/access/resources/downloads.htm

 

[Douglas J. Steele]

Albert's already answered your other question.

I just thought I'd mention the free auto FE updater Tony Toews has at
http://www.granite.ab.ca/access/autofe.htm

 

[Chegu Tom]

Thank You. Another good precaution

Tom

No, you have to use the same version. In addition, I STRONGLY suggest that
you do a de-compile of the application BEFORE
you compile to the mde. I been deploying a number of a2000 mde's created
from a2003 mdb's,, and they been a source of pain
until I started de-compiling the mdb before making the mde.....

You can read/learn about de-compile here:

http://www.mvps.org/access/bugs/bugs0008.htm

and, you can find her a reg edit that adds the de-compile to the right
click menu for windows:

http://www.mvps.org/access/resources/downloads.htm