I'm not sure I understand the reasoning behind splitting the database in the first place. I've never heard of splitting a database for the purpose of cutting down on network traffic. It usually is done to RESTRICT certain users from changing the data.
I assume you have linked your tables to the front end? You cannot make changes in linked tables. I would *unsplit* the database.
I would think that linking would increase network traffic because now you have a connection from the user to theDB, and also the link between the front end and the back end. But I'm no expert in networking.
How many users are using the database? I've been told that Access doesn't do a good job as a back end for more than about 50 users. I'm told that you'dthen want to use SQL as the back end and Access as the front end. But I think that means about a $700 outlay--don't take my word for it, I could have a failing memory.
I'd suggest other ways to reduce network traffic, but don't know your setup ornumber of users. Perhaps a logical help would be to have certain *constant* application users have the software installed to their hard drives and, of course, to restrict certain paths to certain users.
