Karen,
To start with. This procedure is always executed once at the beginning of a session. In normal circumstances the drop will never take place during the session, But there are circumstances thinkable when you like to run it again, that's why I start with a drop. In normal situation the drop is taken place when using disconnect statement Tony From: [email protected] [mailto:[email protected]] On Behalf Of Karen Tellef Sent: donderdag 2 januari 2014 20:01 To: RBASE-L Mailing List Subject: [RBASE-L] - Re: TEMP TABLE Ahhh.... but here we disagree. My "on design eep" (not sure where you're running yours) never has a "drop table" in it, just the "create table". I often have the temp table out there with good data in it for testing, and I don't want to bring a form up in design mode only to find it has dropped my nice table. I just have the "create table" and then it will error because the table already exists. Karen -----Original Message----- From: Tony IJntema <[email protected]> To: RBASE-L Mailing List <[email protected]> Sent: Thu, Jan 2, 2014 12:56 pm Subject: [RBASE-L] - RE: TEMP TABLE To add something completely different to this discussion. Personally I create all the needed temp tables / views in one go using a stored procedure. This procedure starts with a drop (SET ERROR MESSAGE 2038 OFF / SET ERROR MESSAGE 677 OFF) The needed temp tables are also defined as ordinary (most of the time empty, but not always if it is handy to have data available for testing) tables in the database. Then use a project statement to create a temp table. To prevent that rows will exist in the temp tables I am using the statement 'where limit = 0' Create also the necessary indexes in the same procedure. It works perfectly and the nice thing about this is that you are able to have a quick overview of all used temp tables / views and its columns in the whole application and it is also possible to document your used columns with comment in the defined tables. Tony BTW: A happy new year from Holland -----Original Message----- From: [email protected] [mailto:[email protected] <mailto:[email protected]?> ] On Behalf Of Javier Valencia Sent: donderdag 2 januari 2014 19:17 To: RBASE-L Mailing List Subject: [RBASE-L] - RE: TEMP TABLE Jim, What version are you using? Are you by any chance using the command: SET UINOTIF OFF I got a similar message (in the version before the current) when running forms that were using Temporary Tables (and did not have that problem before), right after I added the command above to the startup file. One way to check is to trace the code and just before you execute the DROP command, press the F3 key and check if the temporary table is present. If the table is present and you still get the error and you are using the Setting: SET UINOTIF OFF Try disabling the setting and see if you still get the error. I understand this issue has been fixed in the latest release but I have not had a chance to verify it within my own applications. For the time being, I have simple disabled the setting until I run a more comprehensive test to make sure it works on my current setup. Javier, Javier Valencia, PE O: 913-829-0888 H: 913-397-9605 C: 913-915-3137 -----Original Message----- From: [email protected] [mailto:[email protected] <mailto:[email protected]?> ] On Behalf Of Jim Belisle Sent: Thursday, January 02, 2014 9:22 AM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: TEMP TABLE I have done that. All code works as planned until I come to the last lines that DROP the table. I then get the error message even though I have that message off. James Belisle Making Information Systems People Friendly Since 1990 -----Original Message----- From: [email protected] [mailto:[email protected] <mailto:[email protected]?> ] On Behalf Of Buddy Walker Sent: Thursday, January 02, 2014 9:16 AM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: TEMP TABLE Can you put a "Trace ON' just before calling the form and bit button to step through to see what is happening? -----Original Message----- From: [email protected] [mailto:[email protected] <mailto:[email protected]?> ] On Behalf Of Jim Belisle Sent: Thursday, January 02, 2014 10:12 AM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: TEMP TABLE No disconnect. This is a form within my application. I am just using the CLOSEWINDOW code to get back to the main menu. James Belisle Making Information Systems People Friendly Since 1990 -----Original Message----- From: [email protected] [mailto:[email protected] <mailto:[email protected]?> ] On Behalf Of Buddy Walker Sent: Thursday, January 02, 2014 9:07 AM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: TEMP TABLE Jim Do you disconnect or re-connect to the database in your code is so that could be causing your temp table dropping. Buddy -----Original Message----- From: [email protected] [mailto:[email protected] <mailto:[email protected]?> ] On Behalf Of Jim Belisle Sent: Thursday, January 02, 2014 9:57 AM To: RBASE-L Mailing List Subject: [RBASE-L] - TEMP TABLE I am working with two forms where one form comes (form A) up then when I am finished with form A I close the form and bring up form B. When done working in form B I hit a bit button that closes the window and performs other code. Here is my problem. Form B is based on a temp table and the very last code in the bit button when closing this form is to DROP the temp table. I set the error message 2038 off and the temp table updates the regular tables per the code. However I continue to get the error message 2038 stating the temp table is not defined. Another aspect to this is that this happens ONLY after adding rows to another temp table through a DBGrid on Form B. The error codes do not appear when adding the row. Just when the code runs through the Bit Button. Any suggestions? James Belisle Making Information Systems People Friendly Since 1990
