bb.donnay-software.com

That was correct. But I am having trouble with the call stack. It geneates the line of the lb_warning, then the line calling the function. How do I get the line causing the error, which is a few lines above the recover using. I just forced an assignment error to test. I see the error line in the reg...

My error. the instance variable is args, not arguments.

Thus I generated an error inside my recover using statements.

Cliff

I have the following constructi: bSaveErrorBlock := ErrorBlock( {|e| Break(e) } ) BEGIN SEQUENCE DO WHILE !EOF() SOME CODE SKIP ENDDO RECOVER USING oError WTF oError pause wtf('Arguments: '+dc_xtoc(oError:arguments)) pause wtf('Cargo: '+dc_xtoc(oError:arguments)) pause wtf('Error description: '+dc_x...

Try expanding the oToolBar Size to account for more buttons.

Great list of topics. Wish I was able to attend.

Any info on parsing incoming JSON. I know we have the ability to create JSON.

Cliff

Thanks. That is what I think I need.

Cliff

I am essentially doing that. But I have to put the 2 new functions that are used in 265 into my code which is still running on 264 because the linker needs to see the functions. I do that sort of thing you indicated all the time based on express versions, but I was trying to avoid having to compile ...

No, I need to stub the two function calls. YOu made changes to 265 to put the cursor in get fields at the end of the active data, which is causing me problems. You provided two function calls allowing me to post the old code to revert it to 265 behavior. My current code base is based on 265 but I ha...

Changes were made to Express 265 related the inputfocus code block and highlighting/going to the end of the data field in a get. We are still beta testing 265 and using 264 in production so we need to have the new functions in Express 265 available in Express 264 without recompiling the Express libr...

Try reindexing the file. That is the only time I have seen this, a corrupted index.