My live database is currently not secure.  I have a copy of it that I have
worked out all the security issues and I am ready to update the live data
with the secure schema.  (I had to modify several forms, and queries so that
I could secure the database with the user groups I created)  I now have it
the way I want it, but I am also planning to split the database.  I would
like to know which I should do first.

1. Should I go ahead and implement the security schema alone first?
2. Should I make another copy of the live data and work on splitting and
testing the split, then implement it first then the security later?
3. Should I just continue with my secure database and split and test it,
then implement both at the same time?  I do understand that it is not always
wise to implement multiple major changes at the same time, but with
extensive planning and testing could this work ok?  If I use the database
splitting wizard, is it pretty straigtforward and fool proof or should I
split the database on my own?  Is there anything else to consider when
splitting the database?  Do the links handle everything or do I have to make
any modifications to my code for it to find the tables?  I.E. currently I am
opening tables in code using currentdb.openrecordset... will this need to
change?