Do MDE perform Well with Mulitpul Users

[Deano]

Can anyone tell me how well converting an access dbase into an MDE file,
will work over a network connection with around 5 users accessing at the
same time. There won't be a great deal of access but will be open on 3 or 4
machines all the time during the day.

I am waying up my options (mainly security) whether to split the dbase or
convert to MDE

I will post this question in the security newsgroup aswell.
Thanks for any advice in advance

 

[Douglas J. Steele]

Splitting the database or converting to MDE aren't mutually exclusive.

You should always split the database: you increase the risk of database
corruption significantly if you have more than one user using the same copy
of the database.

Once you've split the database, you can convert the front-end to an MDE and
distribute a copy to each user. There's no point converting the back-end to
an MDE: MDEs are only intended for code, not data.

In the future, if you feel you need to post to more than one group (HINT:
it's seldom necessary), please have the courtesy to cross-post (send the one
message to all groups at once), rather than multi-post (send individual
messages to each group). In this way, all responses to your post will be
available together, regardless of what group the responder was in, and the
rest of us won't have to read your post multiple times. (It also uses fewer
server resources)

I see you're using Outlook Express. Click the "Newsgroups:" label to the
left of the box containing the name of the current newsgroup. That will open
a dialog that will let you add additional newsgroups to your post.

Note that it's generally consider to be A Bad Thing to cross-post to more
than about 2 or 3 newsgroups. (In fact, at
http://www.microsoft.com/presspass/features/2001/Mar01/Mar27pmvp.asp
Microsoft suggests that "One group will suffice")

 

[Nikos Yannacopoulos]

Deano,

If t's going to be multiuser, then you have to split, put the back end
on a file server and distribute a copy of the front end to each user.
The front end can well be an mde. The primary benefit of an .mdb is it
prohibits the user form making design changes. No impact on performance
(or maybe a very small positive one, but would take a very heavy app to
make it apparent). Anyway, for the number of users mention, performance
is no issue with a well-desinged database on a decent LAN.

Check out these valuable links from Tony Toews:

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

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

HTH,
Nikos

 

[Deano]

Thank you for the comments.

I didn't want to offend anyone, hence thats why I added I was posting in
another group. Also thanks for the instruction on how to cross-post - I
didn't know about it at all otherwise I would have used it. I don't
normally post in more than one but I felt that some people only look at
certain newsgroups more than others and by putting it both, I would attract
other peolpe's comments.

But on the whole, thanks for comment's about the original request

Cheers

 

[Deano]

Thanks for Links. I will go with the splits after reading them quickly. It
does offer more functionality on my part (Developement) and at the end of
the day, the data is the most important thing.

Cheers