Appending data to Intranet database

I have a user that is mapping to an Access database on the Intranet server which is fine, but my question is, what is actually happening on the server when they are running appends there? I see the LDB opening and closing as they run their macro. This database is getting large - 164 meg - what impact is this having on the rest of my Intranet performance? How much memory is being used on the server, as opposed to on their workstation? Several times while they were connected to this database, all ASP's stopped working and I suspect they are the cause. This process was inherited and they are being secretive, any suggestions?

Will try to answer based on my understanding your question. Assuming that the server database is a simple back end/front end arrangement of a standard Access database, you ought to be aware that when more than one user is logged in, the performance is going to suffer greatly. The update time depends little on the data being sent over the network. Speed depends more on the server's processor and disk IO and less so because of the workstation. Also, the number of shared applications served by the server affects the performance.

164 MBs sounds quite a lot for an Access application and most likely that the database needs compacting and repair.