Jason and Jan, I think you two hit the nail on the head. I commented the drop table code. Then I realized I should put that code in form A AFTER The EDIT USING form B code. I did not need the drop code in form B.
Now to figure one more item and I should be good to go. James Belisle Making Information Systems People Friendly Since 1990 -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of jan johansen Sent: Thursday, January 02, 2014 10:00 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: TEMP TABLE Jim Put the drop after the code that calls form b. --form a Edit using form b Dtop table temptable Or secondarily put the drop in the On form exit eep of form b Jan -----Original Message----- From: "Jim Belisle" <[email protected]> To: [email protected] (RBASE-L Mailing List) Date: Thu, 2 Jan 2014 08:57:14 -0600 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 > > > > >
