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

Examples Of Larger Systems Built On MDB Backends

P: n/a
I've been asked to build a system that is considerably larger than
anything that I've done before and I'm trying to determine if an mdb
backend is up to it. The system is not mission critical to the point
where the loss of a day's data would be a catastrophe.

It will probably be running on terminal server. If I understand
terminal server correctly this will be slightly more robust than a
frontend/backend setup where each user has the frontend on their
machine. I'm assuming that if the backend and each user's frontend
profile is on the server all the problems that can arise from faulty
network connections etc will be removed.

I'm interested to hear of examples of "large" (a very subjective term)
database systems that have been built by contributors to this forum
that work reliably on an mdb backend.

Any help is appreciated.
Jan 9 '08 #1
Share this Question
Share on Google+
5 Replies


P: n/a
On Tue, 8 Jan 2008 16:32:24 -0800 (PST), Wayne
<cq*******@volcanomail.comwrote:

Let me turn that around and let you give a synopsis of what your app
would do, and how many forms and reports you expect in the final
product. Also how many CONCURRENT users.

-Tom.
>I've been asked to build a system that is considerably larger than
anything that I've done before and I'm trying to determine if an mdb
backend is up to it. The system is not mission critical to the point
where the loss of a day's data would be a catastrophe.

It will probably be running on terminal server. If I understand
terminal server correctly this will be slightly more robust than a
frontend/backend setup where each user has the frontend on their
machine. I'm assuming that if the backend and each user's frontend
profile is on the server all the problems that can arise from faulty
network connections etc will be removed.

I'm interested to hear of examples of "large" (a very subjective term)
database systems that have been built by contributors to this forum
that work reliably on an mdb backend.

Any help is appreciated.
Jan 9 '08 #2

P: n/a
Per Wayne:
>I've been asked to build a system that is considerably larger than
anything that I've done before
Define "larger".
--
PeteCresswell
Jan 9 '08 #3

P: n/a
Wayne wrote:
Thanks Tom and Pete for your replies.

The database would handle production data from pit to port including
tonnages mined, preparation plant data and shipping data.

In very rough terms the database would have about 20 tables, each
table would have no more than a dozen fields. Data entry would be
about 6 records per day into a few of the tables and less than that
for the rest. It would have a about 30 forms, 30 or 40 queries and
about 25 reports. Concurrent users would be less than 6.
That does not meet any reasonable definition of "larger". You should be fine.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com
Jan 9 '08 #4

P: n/a

"Wayne" <cq*******@volcanomail.comwrote in message
news:0a**********************************@s19g2000 prg.googlegroups.com...
It will probably be running on terminal server. If I understand
terminal server correctly this will be slightly more robust than a
frontend/backend setup where each user has the frontend on their
machine. I'm assuming that if the backend and each user's frontend
profile is on the server all the problems that can arise from faulty
network connections etc will be removed.
Each user will get a copy of the front-end in a terminal server enviroment.
Also each Access user needs be treated as a power user when sizing the
server.
Jan 9 '08 #5

P: n/a
Per Wayne:
>In very rough terms the database would have about 20 tables, each
table would have no more than a dozen fields. Data entry would be
about 6 records per day into a few of the tables and less than that
for the rest. It would have a about 30 forms, 30 or 40 queries and
about 25 reports. Concurrent users would be less than 6.
I'd expect no problems with less than 6 concurrent users.

As far as number of tables/fields/forms/queries/reports go, I'd
call that a relatively small application.

The only MDB-specific issues that I can see are:
-----------------------------------------------------------------
1) Unexpected LAN problems. Flaky server, bad NIC, whatever....
But I'm guessing you're in a position to quickly move the back
end to another server, so that's not the potential problem it
would be in a large organization where they have everything
totally locked down and you have to go to committees and wait
for months for a move.

2) IT deploying a later version of MS Access. Minor nuisance,
but it can break an application until somebody makes the
needed adjustments. Again, size of organization...
-----------------------------------------------------------------
--
PeteCresswell
Jan 9 '08 #6

This discussion thread is closed

Replies have been disabled for this discussion.