Terry If you have an MB then yes do put all your workspace statements into it. No need to use a workspace
Not sure if you need to worry about the various directory statements if you are opening tables directly - it depends on how much you want to hard code the paths in your app and where the data is. The function you mention and others like them retrieve registry values so that you can tell the application where to find files which are unique to the user (e.g. the PEN file and the users home directory) - this means you have a more portable app - but you may not need to worry, especially if you have a standard desktop. Paul Crisp BT Syntegra Innovation Place Delta Bank Road Newcastle NE11 9DJ Tel 0191 461 4522 Fax 0191 460 1987 -----Original Message----- From: Terry McDonnell [mailto:[EMAIL PROTECTED] Sent: 28 April 2004 11:41 To: [EMAIL PROTECTED] Subject: RE: MI-L Startup.Wor Paul Thanks for getting back. I'm steering away from trying to control MI from VFP code. You may recall the problems I had with IM. All my control of MI is now in my MB application. Would another slant on your solution then be to transfer my statup.wor code to a MapBasic .MB, which is the first procedure called in my MB application, and then invoke the MB app. from my VFP app., instead of invoking MI (which calls the .wor)? Or via: Run Application "PathToMy\whatever.wor"? I can't find "Home" and "Working" directories via 'Options'/Preferences/System settings', nor via the "Directories" button thereon. Maybe I should point out that I'm using MI 7.0, and that the path to these may be different in your version? As for "MapBasic statements to control them" I can only find functions to find them, such as: HomeDirectory$(). Cheers Terry -----Original Message----- Terry Best thing to do - to have maximum control - is to avoid the use of workspaces when you have your own code you can use. You can take the statements in the workspace file and put them into your Fox Pro code. First line should be "Close All" to shut down any tables, and that is the last thing you tell MapInfo to do before trashing the object reference on the way out - this way you have complete control over map contents and you can also trap the ID of the new map window or windows as they open. Workspaces are very useful - like the MapBasic window - for recording the staments you need to use to repeat results - but I think they are a bit of a vulnerable component in a customised program. Obviously its different if you aren't programing, when they are a valuable tool. The 'home' and 'working' directories crop up on here every now and then - if you open up ordinary MapInfo desktop you'll find these under 'Options'/Preferences/System settings' and there are MapBAsic statements to control them - look at the MB ref (if you haven't got it I believe its a free pdf on the MapInfo site). They get changed around with the user now because of the wonderful world of profiles Paul Crisp --------------------------------------------------------------------- List hosting provided by Directions Magazine | www.directionsmag.com | To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Message number: 11566 ******************************************************************** This email may contain information which is privileged or confidential. If you are not the intended recipient of this email, please notify the sender immediately and delete it without reading, copying, storing, forwarding or disclosing its contents to any other person Thank you Check us out at http://www.btsyntegra.com ********************************************************************
