This is standard procedure. If you are going to autocheck, always reconnect to the database before proceeding.
I like to have a ConnDB.rmd file which I call to connect to a database. It connects to the database, and forces all critical settings to the correct values, just in case the database had the wrong ones stored. I use it in my apps whenever I want to connect/reconnect to a database. It eliminates a host of problems. I would use that before I autocheck. Whenever I run a procedure which requires temporary tables, I run this file and then create the necessary elements. That way, all the temporary stuff is brand new clean and I get no surprises. --Dennis McGrath -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Tom Grimshaw Sent: Friday, November 22, 2002 9:04 PM To: [EMAIL PROTECTED] Subject: RE: Labels G'day Ben, At 18:48 22/11/02 +0000, you wrote: >Can you describe the bug involved in dropping temp tables. I'm >using them a lot in a new app and would like to avoid any known >problems. To this point I've just let them expire on closing the app, >but was thinking of a new process that would involve dropping >some of them routinely. Here's a post from the archives Dan sent: > I have a command that creates a temporary table. > > drop table costtemp nocheck > create temporary table costtemp (serial int) > > First it drops the table in case something happened. > > It works sometimes and doesn't other times. It gives me the multi-user error message > > "Resources required by command are not available" with the "retry" and > "cancel" buttons. > > Then gives me the error > > "Unavailable resource encountered during DROP command(2440)." > > What is unusual is if I turn off the "error messages" setting it will most > of the time work. But if I turn on the "error messages" it will never work. > > Since it is a temporary table it shouldn't be concerned with multi-user > issues. > > Anybody have ideas?? > > Dan Goldberg turns out Dan's problem went away when he changed his rbase.cfg but Dennis McGrath's solution: "Don't drop temporary tables. Just reconnect to you database and all temporary tables and views go away. Nice and clean." was what I implemented as a standard operating procedure with no known adverse issues to date. Just recently we again tried dropping temp tables rather than disconnecting and had reason to do an autocheck after dropping a temp table. Despite dropping it, only after a disconnect did we stop receiving the msg (from memory): "Error in length of DBInfo block." Warmest regards, Tom Grimshaw coy: Just For You Software tel: 612 9552 3311 fax: 612 9566 2164 mobile: 0414 675 903 post: PO Box 470 Glebe NSW 2037 Australia street: 3/66 Wentworth Park Rd Glebe NSW 2037 email: [EMAIL PROTECTED] web: www.just4usoftware.com.au "... the control of impulse -- is the first principle of civilization."-- Will Durant, Pulitzer Prize winning philosopher, writer and historian the most needed product in the world can be found at www.thewaytohappiness.org This email and any files transmitted with it are confidential to the intended recipient and may be privileged. If you have received this email inadvertently or you are not the intended recipient, you may not disseminate, distribute, copy or in any way rely on it. Further, you should notify the sender immediately and delete the email from your computer. Whilst we have taken precautions to alert us to the presence of computer viruses, we cannot guarantee that this email and any files transmitted with it are free from such viruses. ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/ ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
