using spanish language with flashreports by tufat.com

First ANY multi-user database NEEDS to be split, no ifs, ands or buts. So I won't even deal with the issue of an unsplit database.

However, the front end does not have to be local. It can be shared. Having it local is the recommended usage, but if there will not be a lot of concurrent usage it can be shared.

When you run a Make Table query it MAKES a table. The table exists like any other. What makes it a temp table is its usage. I'll give you an example. I have an app that processes invoices from our various car services. The invoices come in electronic format and I input them into a temporary table. After import the user checks the numbers and prints a report for dept review. Then the data in the temp table is added to a history table. The next invoice overwrites the data in the temp table. That's what makes it temporary.

A recordset, on the other hand is a temporary construct more like what you describe in mainframe database. But you have to remember that Access was designed primarlily as an end user/small workgroup database. So it shouldn't be compared to things like DB2.

Frankly, I'm not sure how Access would manage variables like that. Im not sure where they are stored (in RAM in the MDB or what). The only thing I can suggest is to experiment.

Hope this helps,
Scott<>