Free Lessons
Fast Tips
Topic Index
Home   Courses   Index   Templates   Seminars   TechHelp   Forums   Help   Contact   Join   Order   Logon  
Home > TechHelp > Directory > Access > Split Database < Nested Subforms | Update Query >
Back to Split Your Database    Comments List
A local table Upload Images   Link   Email  
Thomas Gonder       
2 years ago
I  have two "control" tables. One meant for the BE (backend) and one for the FE (frontend). What's the best way, either before or after the split, to keep that one FE table local?
Dan Jackson              
2 years ago
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
Scott Axton            
2 years ago
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.
Thomas Gonder       
2 years ago
@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.

This thread is now CLOSED. If you wish to comment, start a NEW discussion in Split Your Database.


The following is a paid advertisement
Computer Learning Zone is not responsible for any content shown or offers made by these ads.

Access - index
Excel - index
Word - index
Windows - index
PowerPoint - index
Photoshop - index
Visual Basic - index
ASP - index
My Account
My Courses
Lost Password
Student Databases
Change Email
Latest News
New Releases
User Forums
Topic Glossary
Tips & Tricks
Search The Site
Code Vault
Collapse Menus
Customer Support
Web Site Tour
Consulting Services
Affiliate Program
Richard Rost
Free Lessons
Mailing List
Video Tutorials
Learning Connection
Idiot's Guide to Excel
Volume Discounts
Payment Info
Terms of Sale
Contact Info
Support Policy
Mailing Address
Phone Number
Fax Number
Course Survey
Email Richard
[email protected]
Blog RSS Feed    YouTube Channel

Copyright 2024 by Computer Learning Zone, Amicron, and Richard Rost. All Rights Reserved. Current Time: 6/19/2024 11:35:38 PM. PLT: 2s