Jane,
Also,
it can depend on the size of your backend (sounds kind of personal, doesn't
it?). The larger the mdb file, the slower it will compact. Depending
on your environment, it might not compact after reaching a certain size without
jumping through a lot of hoops. I had one project on a Novell network that
started getting weird around 30MB and simply refused to compact at all at
80MB.
Far
Farley
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED]On Behalf Of Tom Oakes
Sent: Tuesday, October 18, 2005 2:03 PM
To: [email protected]
Subject: RE: [AccessDevelopers] Multiple BE vs one BEThe main disadvantage is that you cannot enforce referential integrity between multiple backends.I'm forced to do things with multiple backends for one of my clients. You just need to manage your interfaces so that you maintain integrity as you would with relationships.Tom Oakes
Personal PC Consultants, Inc.
[EMAIL PROTECTED]
503.230.0911 (O)
402.968.6946 (C)
734.264.0911 (F)
Are there any advantages/disadvantages in keeping all the data tables
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of vjcross2004
Sent: Tuesday, October 18, 2005 6:19 AM
To: [email protected]
Subject: [AccessDevelopers] Multiple BE vs one BE
in one back end file as opposed to splitting the biggest data tables
into their own BE?
Or does it make no difference?
Jane
Please zip all files prior to uploading to Files section.
SPONSORED LINKS
Microsoft access developer Microsoft access help Microsoft access database Microsoft access training Microsoft access training course Microsoft access programming
YAHOO! GROUPS LINKS
- Visit your group "AccessDevelopers" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
