RE: Multiple MDB files???

Tech-Archive recommends: Fix windows errors by optimizing your registry



It is definately better because it doesn't have all of your eggs in one
basket. Furthermore when you update information in a single table, you are
updating a smaller file altogether. However you may also encounter a
reduction in speed when another user goes to open up the same file that is
already open by another user. To work around this just open up a table in
each mdb when the program loads.
For more information on that check out Tony's page at
http://www.granite.ab.ca/access/performanceldblocking.htm

Good Luck, BTW we have 27 back end mdb files. Some still get very large.

"brba" wrote:

> I have a databse with an Access front-end on everyone's individual PC sharing
> an Access back-end on the server. The tables in the back-end data file are
> linked into the front-end. As we increase the functions of the database, and
> thusly the number of tables (currently my question is whether or not it makes
> more sense to create multiple back-end data files or if just one would be OK.
> RIght now, my back-end is 32MB in size...not large, but getting larger every
> day. I'm leaning towards splitting the back-end into about 5 different files
> and repointing the links.
>
> Any comments?
.



Relevant Pages

  • Re: Multiple MDB files???
    ... databases often are.) ... rather than allenbrowne at mvps dot org. ... >I have a databse with an Access front-end on everyone's individual PC ... The tables in the back-end data file ...
    (microsoft.public.access.tablesdbdesign)
  • Multiple MDB files???
    ... I have a databse with an Access front-end on everyone's individual PC sharing ... an Access back-end on the server. ... The tables in the back-end data file are ...
    (microsoft.public.access.tablesdbdesign)