Re: Multiple MDB files???

Why do you not enforce referential integrity?

If size is an issue use SQLS2000 or DB2 but NEVER have related tables in
different MDBs.

Your advice is absolutely wrong, if you care about the data. If you could
not give a damn about data consistency then your advice would certainly help
ensure the data could become inconsistent.

--
Slainte

Craig Alexander Morrison
Crawbridge Data (Scotland) Limited
"Scott N Weber, MCP" <ScottNWeberMCP@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:5CA7D4E0-F407-40C1-89A5-690E33CAA581@xxxxxxxxxxxxxxxx
> 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

  • How to prevent savy users from linking to BE tables?
    ... and obtains a copy of the master FE .mdb if the version is different. ... The FE has the shift-key and F11 database window key disabled. ... the data is stored (back-end tables), they can create an .mdb that has linked ... folder that the users have full rights to, otherwise they won't be able to ...
    (microsoft.public.access.security)
  • Re: Code Issues
    ... It may well be a good idea for you to do what Salad suggested and create a new mdb and make sure autocorrect is turned off. ... I'm not sure if a decompile would be necessary after doing this, but I don't think it will hurt. ... In A2003, I'm lucky to get anywhere near this size, though the big front enc app ... I also second Darryl's advice, I've run into irritating problems like he describes many times in the versions of Access I've used. ...
    (comp.databases.ms-access)
  • Re: After MDW setup in local, how can I move it to companys intra
    ... > everything (mdb and mdw) to the designated server drive? ... I never think about seperated front-end and back-end, ... >> The MDW should move with the MDB: all users will require Read, Write, ... >> Doug Steele, Microsoft Access MVP ...
    (microsoft.public.access.security)
  • Opening multiple mdbs
    ... use an Access front-end for the code, and an Access back-end for the ... another mdb for a large quantity of temporary data. ... "temp" mdb, but could never create the necessary table. ...
    (microsoft.public.access.modulesdaovba)
  • User-defined functions
    ... I'm a very new learner in SQL Server 2000 now - Can I link to user-defined ... functions for an Access front-end .mdb just as with SQL Server Views? ... that functions are used with Access projects, ...
    (microsoft.public.sqlserver.programming)