temp tbl

[slimjen]

All, using access 2010. I have code to delete a temp file before processing more code.

DoCmd.DeleteObject
acTable, "tbl_temp"

Sometimes; users would start the process and stop for some reason or another. This doesn’t happen often but I would like to avoid the errors. What happens now is a pop up tells them the temp table is not found and just hangs. I know I need to put error trapping but need the correct error trapping. I want them to be able to go beyond that point. Ideally; I want them to not even become aware that the table is not there but just go on to the next step without them knowing the table is not there. Can anyone help with error trapping and message pls.

[pbaldy]

You can add normal error handling:

http://www.baldyweb.com/ErrorTrap.htm

but for that specific error number use

Resume Next

and no message box.

[ssanfu]

Sounds like you are using a make table query. I don't use make table queries because they have been known to cause corruption. Also, constantly creating and deleting tables causes dB bloat.

I create the temp table, then delete all records before I append the new data.
If a table is being created over and over, it is important to create it once and just delete the records..(IMO)


My $0.02....

[June7]

I also use temp table - 'temp' means records are temporary, not the table. As Steve said, just purge the table before the process that uses it. No error.

Also, if this is a split db (should be with multiple users), the temp table goes in the frontend.

[slimjen]

Ok. The temp table is in the frontend used to import data and in case there are errors we can catch before appending to the main tbl. But as stated; a user may start the code which is to delete the old temp table then realize something or some other reason stop the next part of the code from running. Then upon the return to run the code, the temp table is not there and the code does not go forward. I'll try the error handling with resume next. I thought there was a way to just skip that part of the code and go on since this is the first step in the code and doesn't matter if there is a temp tbl because it would be replace anyway. Thanks

[June7]

Still advise is best to just delete records then there will not be an error to deal with. Also, eliminates the issues of db corruption and bloat.

[slimjen]

so delete records and append the data? No use for temp tbl????

[June7]

Did not say that. Use temp table but don't delete and re-create table. Delete records from temp table.

[ssanfu]

I totally agree with June. That is the way I use the temp table. Delete the records, NOT the table.

[slimjen]

Thanks All!