By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,495 Members | 1,146 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,495 IT Pros & Developers. It's quick & easy.

Split Database: Single Front End

P: n/a
I have read that using the database splitter is good because it allows
multiple users to access the database simultaneously. However, is it
trully necessary to have multiple FE MDE files or can everyone just use
a single MDE file that is located on the network drive?

Jan 9 '07 #1
Share this Question
Share on Google+
3 Replies


P: n/a
Nubs wrote:
>I have read that using the database splitter is good because it allows
multiple users to access the database simultaneously. However, is it
trully necessary to have multiple FE MDE files or can everyone just use
a single MDE file that is located on the network drive?

Reportedly, it's possible to have a single copy of the FE on
a server if you follow all the rules about multiple
instances modifying the same objects at the same time.

Personally, I think it's near impossible for an app with a
reasonable set of features to avoid all the potential
pitfalls. I would not want to wait around for the crash,
data munge, or corruption caused by something that I was
unaware would be a problem.

--
Marsh
Jan 9 '07 #2

P: n/a
"Nubs" <bu******@gmail.comwrote in news:1168370919.425443.164210
@k58g2000hse.googlegroups.com:
I have read that using the database splitter is good because it allows
multiple users to access the database simultaneously. However, is it
trully necessary to have multiple FE MDE files or can everyone just use
a single MDE file that is located on the network drive?
Suppose there's a love-letter module that uses a user defined database or
application property named "LightofMyLife" for the e-mail address.
I set this property to Ru**@Red.Com.
You set it to Bl****@Fox.Com.

I send my love letter. Who will get it?

I don't know.

And I don't want to find out.

--
lyle fairfield
Jan 9 '07 #3

P: n/a
"Nubs" <bu******@gmail.comwrote
I have read that using the database splitter is good because it allows
multiple users to access the database simultaneously. However, is it
trully necessary to have multiple FE MDE files or can everyone just use
a single MDE file that is located on the network drive?
Firstly, that is not what allows multiple users to access the database
simultaneously. You can put a monolithic (unsplit) database on the server
and let all the users log in to that, and, much of the time, it will work.
But, when you do experience corruption, and that is likely, not only will
you need to restore the front-end, you'll have to recover your data (at
least, update it from the time of the last backup).

And, in addition to Marshall's comments, empirical evidence is that you
significantly increase the chance of corruption of any MDB (even a
front-end) when you have multiple users logged in at the same time. Then the
shared front-end will have to be restored, before _any_ user can access the
database.

So, I'd say, perhaps not necessary, but for many reasons, advisable.

Larry Linson
Microsoft Access MVP
Jan 9 '07 #4

This discussion thread is closed

Replies have been disabled for this discussion.