06-08-04, 20:12 #1Registered User
- Join Date
- Oct 2003
Unanswered: Database splitting - more than one data file
I currently have a database which is split into a front end mde application and a back end mdb data file. Recent events and corruptions have prompted me to consider splitting the back end database further. i.e. A data file for each main section (around 4-5).
Can this be done? If so, what things do I need to consider and is this a wise decision?
I have a setup of around 30 users. 15 connected through Terminal Services and 15 standalone PC's running a copy of access runtime. Runtime doesn't allow me to go into linked table manager so I would need a way around that.
Any advice or comments are welcome. Thanks in advance.
06-09-04, 01:18 #2(Making Your Life Easy)
Provided Answers: 10
- Join Date
- Feb 2004
- New Zealand
Yes it can be done
What I did was
Have is a Event Report System Link to
a Event Data Backend , Hazard Management Backend,Training Data Backend
Also each one have there own frount end Linking to each other
There about 6 year work There it groven over the Yearshope this help
the aim is store once, not store multiple times
Remember... Optimize 'til you die!
Access based on my own environment: DAO3.6/A97/A2000/A2003/A2007/A2010
VB-NET based on my own environment started 2007
SQL-2005 based on my own environment started 2008
YOUR PASSWORD IS JUST LIKE YOUR TOOTHBRUSH DON'T SHARE IT.
DONT WORRY ABOUT THOSE WHO TALK BEHIND YOUR BACK
THEY'RE BEHIND YOU FOR A REASON