Re: MS Access question

Post #350,103 by altmann 11/3/11 5:56:21 PM Reply	Re: MS Access question A couple of ideas: 1) add a user field to the records in the temp table. 2) name the temp tables after the user 3) separate your front end .mdb(code, queries, reports, etc) from the back end (shared tables) and create the temp tables in each user's front end. Then use linked tables to tie the two together. 4) put the temp tables in a separate .mdb organized by one of the above methods. 3 and possibly 4 are probably your best bets. You'll want to account for the need for occasional db compaction wherever those temp tables end up too.
Post #350,112 by scoenye 11/3/11 9:16:14 PM Reply	3 is the way But do you really need the results as tables? It is not that the users can take off with them as they would with Excel files unless the contents are exported. A view/query resultset would not have the problems you describe and the results can be exported as well. Of course, Access across a network is always fun. Better not have a T1 in there...
Post #350,122 by malraux 11/3/11 10:24:35 PM Reply	Yep But like you said, once you get to the point where the application requires splitting the MDB up, you're using the wrong tool for the job. Regards, -scott Welcome to Rivendell, Mr. Anderson.

Welcome to IWETHEY!