Access and VBA structure for web-client integration later on?
I'm developing an Access database that pulls variables via ODBC, receives input from end users, and uses the variables from both to do a calculation. The best way to explain the process is that it's similar to a 1040 tax form (not exactly, but the concept is the same). ODBC pulls W2 information, user views the records to determine what action needs to be taken, enters a status that impacts what calculations are run, and the calculations spit out half a dozen variables that need to be stored for audit purposes and merged onto printed documents for the client. 

The structure I have is ODBC that's read only, back-end accdb for data, and a front-end client for the end-user. This database is expected to be used for at least 2-4 years, where it then will be considered for our main software that is moving from Unisys to web based. 

With that in mind, what is the best structure when developing in Access? Should I focus on placing as much of the code as possible in public modules or should they be more in make-table queries? Should I avoid storing variables in the code and have tables for every variable needed?
Access and VBA structure for web-client integration later on?
===

I'm developing an Access database that pulls variables via ODBC, receives input from end users, and uses the variables from both to do a calculation. The best way to explain the process is that it's similar to a 1040 tax form (not exactly, but the concept is the same). ODBC pulls W2 information, user views the records to determine what action needs to be taken, enters a status that impacts what calculations are run, and the calculations spit out half a dozen variables that need to be stored for audit purposes and merged onto printed documents for the client. 

The structure I have is ODBC that's read only, back-end accdb for data, and a front-end client for the end-user. This database is expected to be used for at least 2-4 years, where it then will be considered for our main software that is moving from Unisys to web based. 

With that in mind, what is the best structure when developing in Access? Should I focus on placing as much of the code as possible in public modules or should they be more in make-table queries? Should I avoid storing variables in the code and have tables for every variable needed?