Perhaps I misunderstand your intention, but it sounds like you are
attemping to create a temporary table to be used as the basis of a
report. If that's the case, and if the temporary table is intended
*only* for that single user, then it is quite acceptable to store the
table in the local (FE) database. No need to store the temp table in
the shared BE.

Even better, create a "temp" MDB file on the local machine, and store
the table in *that* MDB file to avoid "churn" in the FE. A single FE
can use tables from multiple BE's.

--
jackmacMACdonald@telusTELUS.net
remove uppercase letters for true email
http://www.geocities.com/jacksonmacd/ for info on MS Access security

Jeff,
The structure of the report is not going to change.  "Run-Time Error 3009:
You tried to lock table 'tblWhySplitDatbasesAnnoyMe' while opening it, but it
was in use by another user.  Go online to rant for a while, and then try the
operation again."
All I'm trying to do is this:
Sub SendRefreshedDataToBackEnd()        
           DoCmd.CopyObject "db1_be", "ReportData", acTable, "TempReportData"
End Sub

If I could just put the TempReportData into the Backend ReportData table
that everyone runs their reports on, I'd be golden.  The responses I've
gotten when posting this question have been "Well of course, you can't modify
a table's structure while it's in use!"  Well, if I split a database to make
this possible and you say it's not possible, then why did I have the bowl,
Jeff?  Why did I have the bowl?!

Are they just the tool of a false god?  I split my database, and all I got
was this lousy backend.  Front End on each user's C:\ Drive.  Back End on the
shared network.  My Front End runs a query that replaces a table's contents
with updated data.  If I can't modify a table's structure while it is in use,
then what's the point?  Excuse me while I tinker with this thing, and pardon
me if I seem jaded.
inb4 SQL Server...
Poster: "My wife left me"
Aaron: "Switch to SQL Server"