mixmam .mdb size ?

[Guest]

pls i want to know what is the mixmam size for mdb file working from server
becuse i have 8 pc working with access program and the mdb file is sharing
from server so when my mdb file become a 345 mb the applaction become very
sloly and icant still working in the program so how i can solve this issue
regards
khaled

 

[Douglas J Steele]

Assuming you mean maximum size, for Access 2000 and newer, it's 2 Gb.

Note that your application should be split into a front-end (containing the
queries, forms, reports, macros and modules), linked to a back-end
(containing the tables and relations). Only the back-end should be on the
server: each user should have his/her own copy of the front-end, preferably
on their hard drive.

 

[Guest]

Hi Khaled,

The maximum mdb size is 2Gb, however mdb's over 100Mb start showing
performance degradations. A couple of suggestions: Compact the mdb on a
regular basis. Upgrade the mdb to an adp (Requires SQL Server or MSDE; see
http://www.microsoft.com/downloads/...d1-a0bc-479f-bafa-e4b278eb9147&displaylang=en)

I hope this helps.

 

[Roger Carlson]

The maximum size of an Access database (A2000 and up) is 2GB. 345MB is not
all that large.

Questions:
1) Is the database "split" into a Front-End (FE) and a Back-End (BE)?

This is the best physical model for an Access application. The ideas is
your application is in two parts: the FE contains the forms, queries,
reports, macros, and code and the BE contains only the tables. The tables
are then Linked from the BE into the FE. Put the BE on the network and but
a copy of the FE on each user's workstation. (An alternative is to put a
copy of the FE in a separate directory, one per user, on the network.)

2) Have you Compacted the database? A database can grow dynamically as you
add records, but it will not shrink automatically when you delete them. You
have to compact the database to recover unused space.

--
--Roger Carlson
MS Access MVP
Access Database Samples: www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/wa.exe?SUBED1=ACCESS-L

 

[Guest]

Your database can get 5 times larger before exceeding the 2 GB limit for an
mdb file.

Performance problems are more of a matter of database design than size. It
could even be a network problem.

As Doug Steele suggested, splitting the database is a very good idea in a
multi-user environment.

Proper referential integrity and relationships in the Relationship window
can really speed things up especially as primary keys are indexed.

Speaking of indexes, look at all the criteria in your queries. If the table
in question is large, say over 1,000 records, those fields with criteria
should be indexed. This can sometimes really speed up select statements
although there is a possibility that the indexes could slow down inserts and
updates. It will also make your database larger.

 

[Roger Carlson]

I have to disagree. There is no reason that an MDB has to show performance
degradation at 100MB. That wasn't even true of Access 2.0, let alone later
versions. Performance is largely determined by how you develop your
application.

Secondly, there is no guarantee that "upgrading" from Jet to MSDE will
automatically improve performance. Sometimes, it's just the opposite.
Regardless, a poorly designed application will perform poorly, even if the
engine is SQL Server.

--
--Roger Carlson
MS Access MVP
Access Database Samples: www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/wa.exe?SUBED1=ACCESS-L

 

[Tony Toews]

however mdb's over 100Mb start showing
performance degradations.

Agreed with Roger's comments.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[Tony Toews]

pls i want to know what is the mixmam size for mdb file working from server
becuse i have 8 pc working with access program and the mdb file is sharing
from server so when my mdb file become a 345 mb the applaction become very
sloly and icant still working in the program so how i can solve this issue
regards

Now one client did suddenly have performance problems with a 300 or
400 Mb backend. Compacting didn't solve the performance problem.
But importing all the objects into another database did solve the
performance problem.

Why? I have no idea.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[aaron.kempf]

good stuff

sounds to me like you kids spend too much time with workaroudns

access data projects?

we dont have to deal with BUGS like this