creating a table for every user(table name is his session id).<BR>after the manipulations(when the user reaches the final page), the table has to be dropped.this works with sqlsrvr.why now with access db?
Why not store a single table with a Session ID in it?<BR><BR>A table per user is just terribly inefficient. I wouldn't even suggest it with SQL Server.<BR><BR>As for why it isn't working - I have no idea. DROP TABLE tablename is the syntax for MS Access.<BR><BR>I think that you should definately rethink your process. This can all be accomplished in a single table.<BR><BR>-Doug