You would just set up the table on your front end file. You would use the Link Table Manager to connect the back end table
If you're referring to storage, that depends on your setup. Are you using on multiple PC's? Access Updater. If you're just using it on one, store it anywhere on your PC

Not quite sure what you mean by "control table" but... In a split db the BE only contains your tables (data).
The FE contains everything else.  Forms, Queries, Reports, programming.

I always keep both the FE and BE in the same folder on the server with the correct links.
When I deploy the FE to a new computer I make a copy of the FE and place it on the new computer.  I never use or link to the FE on the Server. That way if the user copy gets hosed in some way you just copy a new FE to that computer.

Of course you have to make sure the trusted location is set for the server location so you don't run into security warnings.

BTW I recommend being substantially complete with functionality before splitting your db.  Its just easier if you need to make table changes.

@Dan Unless I missed something in the video, I think all files get moved to the BE. I don't recall an option to exclude certain files.

@Scott A control file contains data specific to the local FE, like user data and country/language options. Thanks for your idea on waiting to split. It's enough work now in development, that I don't need more headaches. Many have told me to split early on, but I'm guessing they aren't in a heavy development cycle with hundreds of tables that are constantly changing.