Rachael - I drop and create temp tables while in a form with no
(apparent/known) problems.
Just CLOSE the table first:
PROPERTY TABLE RcvRecrd 'CLOSE'
SET ERROR MESSAGE 2038 OFF
DROP TABLE RcvRecrd
SET ERROR MESSAGE 2038 ON
CREATE TEMP TABLE `RcvRecrd` +
(`TxnHistSeqNbr` INTEGER, +
... etc )
PROPERTY TABLE RcvRecrd 'OPEN'
CREATE INDEX TrailerNbr ON RcvRecrd (TrailerNbr ASC SIZE 12)
AUTONUM TxnHistSeqNbr IN RcvRecrd USING 1
The form is based on the temporary RcvRecrd table.
AUTONUM & CREATE INDEX commands work ok too, run them after the
table is opened.
Like I said, no apparent or known problems, but now I'm wondering if I
might be asking for trouble since the form is based on the table that
is dropped and recreated while in the form.
Comments anyone?
Doug
Rachael Malberg wrote:
so had to go back in code history
and see how and why I would get those errors so frequently. Turns out
I was running the drop and create code on a forms 'on start eep...' and
another drop command on the form's 'on close eep' Which would mean I
was dropping a table with a lock on it.
I have since stopped doing that and
manage all temp data prior to calling a form/report so I bet the drop
will work much better now. I'm going to add it back in some areas and
see how it goes even though the client is dropping this project due to
these errors, lock ups and autonumber/index issues personally it be
nice if I could get it to work just so I could be comfortable doing
another project in this platform.
----- Original Message -----
Sent:
Wednesday, January 27, 2010 3:36 PM
Subject:
[RBASE-L] - Re: seem to be getting I/O errors when updating temp tables
o...
If you're getting a 'unavailable
resources encountered during drop command', I'd be willing to bet you
have a cursor on the temp table that hasn't been dropped ... I'd look
at all the cursors you might run on that temp table and make sure there
is a drop after it. Then I'd go back to dropping the table each time.
Karen
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.
|
