Hi Milo, One way to make Pro a little more intelligent about trapping errors is the deligate the execution to an mbx and trap the error in that. Each mbx (MBApplications collection in VB) has DO and EVAL, same as Pro itself. The equivalent routines in the mb app is RemoteMsgHandler and RemoteQueryHandler.
Then you can return any error in either an mb global variable (MBGlobals collection in VB) or directly from the RemoteQueryHandler if you swap the DO to be an EVAL. Best regards/Med venlig hilsen Lars V. Nielsen GisPro, Denmark http://www.gispro.dk/ ----- Original Message ----- From: "Milo van der Linden" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Monday, August 15, 2005 10:39 AM Subject: MI-L VB trap MI error (OLE, Integrated mapping) Dear Listmembers, I have a Visual basic application that uses the MapInfo.do statement to open tables in MapInfo. During the opening of a certain table I get several index errors "cannot find index for column Pietje". I want to get these errors into visual basic because now they are causing my application to halt and the mapinfo dialogs are drawn in the back so I can't press the ok button upon them... Is there a way to let MapInfo parse these errors to my visual basic application instead of showing it's own error dialogs? Is there a construction similar to "set progressbars off" for MapInfo's common dialogs? In the MapBasic helpfile this isn't described clear enough to use. Kind regards, Milo van der Linden --------------------------------------------------------------------- List hosting provided by Directions Magazine | www.directionsmag.com | To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Message number: 17484 --------------------------------------------------------------------- List hosting provided by Directions Magazine | www.directionsmag.com | To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Message number: 17486
