Further to Razzaks' information below: In your code use the following before creating a table:
SET ERROR MESSAGE 2038 OFF DROP TABLE XXXX SET ERROR MESSAGE 2038 ON CREATE TABLE.... In addition for additional flexibility in debugging use the following syntax: DEBUG SET TRACE ON ...do your stuff DEBUG SET TRACE OFF Before starting your debug session either set debug on or off. Regards, Ken ----- Original Message ----- From: "A. Razzak Memon" Date: Friday, July 31, 2009 3:38 pm Subject: [RBASE-L] - RE: 7.6 - Form - Trace Behavior To: [email protected] (RBASE-L Mailing List) > At 03:22 PM 7/31/2009, Paul InterlockInfo wrote: > > >While doing a trace I get an error New Table is a duplicate at > >line 31 Ok where is line 31. If you look below I do have a project > >statement however only On Before Design. > > > >This form is based off a temp table and is projected prior in code > >before the edit using this form_name I placed the trace on a > >BitButton and it starts another form to edit based off the same temp > >table. It is then I get this error message. Perhaps I am > seeing too > >much and this is a regular thing happening? With Temp Tables. > It all > >seems to work fine but I also try to watch network traffic and > >well you know. > > > >So do I need to find the answer or is this normal? > > Paul, > > When TRACing a code stored within an EEP, the best option is to use > the Conditional TRACE option. > > Here's how: > > Use the following command at the line where you would like to start > the TRACE. > > SET TRACE ON > > -- your code here .. > > Use the following command at the line where you would like to end > the TRACE. > > SET TRACE OFF > > This technique will allow you to conditionally TRACE the specific > code in an EEP defined as custom code within an object. > > That is your tip of the day! > > Have a great and very productive weekend! > > Very Best R:egards, > > Razzak. > > >
