You should only get 'unavailable resources encountered during drop command'
if the table still has a cursor on it and since the temp tables are local to
the user (and truly local if you have your scratch settings pointing to the
local machine), the only cursor that can be open would be as a result of the
local action, not another user.
I'm with Karen on this one, drop the table over delete records.
----- Original Message -----
From: "Rachael Malberg" <[email protected]>
To: "RBASE-L Mailing List" <[email protected]>
Sent: Wednesday, January 27, 2010 3:27 PM
Subject: [RBASE-L] - Re: seem to be getting I/O errors when updating temp
tables on oc...
Thanks Karen for the reply. I know these errors are a mystery so love any
ideas...
well I too used to do a 'drop table...' but I got so many 'unavailable
resources encountered during drop command' then a 'duplicate table' error
that I went this route instead. The other kicker is these errors will
happen in random instances. It could be the first time ran or later or even
once in a great while, won't error all day. I'm bringing in the network guy
to check 'stuff' out but it is a head scratcher.
----- Original Message -----
From: [email protected]
To: RBASE-L Mailing List
Sent: Wednesday, January 27, 2010 1:23 PM
Subject: [RBASE-L] - Re: seem to be getting I/O errors when updating temp
tables on oc...
Rachel: I didn't read thru all your code, only the very beginning.
But we've had this discussion before on this list -- I see that you
either create the temp table if it isn't there, or delete rows from the
table if it is there. I am one of those people who ALWAYS recreate
temp tables, never deleting rows from the table except for a few
deletes during the processing. If this program is run several times
from the same machine without a database disconnect, so a bunch
of deletes of all rows, there's a good chance at some point you will
get a corrupted temp table in my experience.
Karen
