MS Access XP database installed on Win 2000 Server. It's an important database, but not mission-critical. Presently only four workstations have access to it, and about half my day I'm generally the only one in there, so development work isn't a problem.
Over the next few months we'll be expanding permission to several additional workstations, and providing remote access through our VPN, so I anticipate increasing problems with Access' locking the database when in design mode and preventing saves when others are in the database.
This appears to be precisely why MS provides the Split Database option. I'm hoping for input as to whether there are potential pitfalls to splitting the database in a fairly small network (even with the remote access, I should still have the database largely to myself in the mornings), or whether this is simply a no-brainer.
I seem to recall hearing about some issues with splitting in the newsgroups, so I'm looking for some reassurance before I commit to it.
Thanks for your time!
Free Guide: Managing storage for virtual environments
Complete a brief survey to get a complimentary 70-page whitepaper featuring the best methods and solutions for your virtual environment, as well as hypervisor-specific management advice from TechTarget experts. Don’t miss out on this exclusive content!