I'm deploying a frontend (FE) mdb and backend (BE) mdb in a network environment.

I'm going back and forth with where the application tables should be stored.

If I store them in the BE, then the update procedures that occur in the BE should benefit in terms of speed, but it seems the FE will suffer the possibility of latency.

Conversely, if I sore the tables in the FE, then the USERs will benefit in terms of application speed, but it seems that it would take BE longer to run through update procedures.

Are there standard practices here?

Thanks.

Noel

If you don't have the tables in the BackEnd then what would be in there? Is this a multi-user application?

multiple users can open the FE, but only one user can open and operate the BE at a time.

The BE mainly has a procedure to go out and get a foxpro table(s), import it into access and then update various access tables.

...but only one user can open and operate the BE at a time.
On purpose? Don't you need to share the BE tables with all of the users? It sounds like *your* BE is really being used as a library of code and functions. That's fine but not a typical BackEnd.
Here's some links if you didn't have them already:
Split your Access database into data and application (http://allenbrowne.com/ser-01.html)
Splitting your Microsoft Access MDB into a front end and back end (http://www.granite.ab.ca/access/splitapp/index.htm)