Forums
New posts
Search forums
Members
Current visitors
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Forums
Archive
Newsgroup Archive
Access Newsgroups
Access Table Design
Architectural Issue
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
Reply to thread
Message
[QUOTE="Jeff Boyce, post: 2577216"] I suspect you'll find that you end up with more overhead and more maintenance and more coordination needed by using two front-end portions than just putting it all in one. Have you done any searching on line on these topics? You realize that you posted your "front-end" size question in a "back-end"/tables newsgroup, right? If your tables are well-normalized, and indexed properly for the mix of data-entry and data reporting that your application needs to support, I don't believe you'll see performance issues. If your new functionality is not needed by all users, consider encapsulating the procedures in a module of their own. That way, that portion won't load until the feature set is called for. Good luck! Regards Jeff Boyce Microsoft Office/Access MVP [/QUOTE]
Verification
Post reply
Forums
Archive
Newsgroup Archive
Access Newsgroups
Access Table Design
Architectural Issue
Top