In general, I dislike the concept of using temporary data; however, there are
times when I find it better than the alternatives (such as when attempting to
update a table and using a join to a DISTINCT query as a way to filter the
records, which will not allow an update).

In this case, I am using a table that I empty, then populate, then empty
again when done. For this particular process, although in a multi-user
environment, I have ensured that only one user is running the process at any
one time, because it also involves temporary updates to fields in other
(permanent) tables.

The question: is it better to have the table housing the temporary data in
the FE or the BE?

Pros for the FE: could be a little faster for the user, since the data does
not have to be pushed across the network to the BE.

Pros for the BE: this file is far more likely to get compacted than the FE,
and therefore the bloat inherent (I think) in adding/removing this temporary
data on a daily basis will more naturally be worked out of the system.

Hmmm...nothing here to push me strongly one way or t'other. Am I missing
something (like a better way to accomplish the underlying task)?