Here here, Why o why have they designed newer versions of MI prof. so that you cannot open workspaces and mapbasic programs in older versions of MI Pro. Stinks a bit to me of this idea that you have to go out and buy the newest version of MI pro if you want everything to run smoothly.
Daniel Irwin GIS Officer Transport for London Street Management Software Services - IS/IT Department 25 Eccleston Place London SW1P 1SB Tel: 020-7941-2316 > -----Original Message----- > From: Richard Dibley [SMTP:[EMAIL PROTECTED]] > Sent: 31 January 2002 09:54 > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: RE: MI-L RE: MapInfo 6.5 , 6.0 , 5.5 compatibility > > I have no problem with backwards compatibility in MapInfo regarding > opening old Workspaces. But why oh why can't I tell MapInfo 6.5 to save > a workspace in an older workspace format? > > I know I can edit the workspace in a text editor but that is, frankly, a > pain in the ass. > > This has to be high on my wish list. > > > Richard > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] On Behalf Of > [EMAIL PROTECTED] > Sent: 30 January 2002 21:55 > To: [EMAIL PROTECTED] > Subject: Re: MI-L RE: MapInfo 6.5 , 6.0 , 5.5 compatibility > > > Valued MI-L Members, > > First, please let me answer the original question of compatibility: > > MapInfo Professional always had and will continue to have backwards > compatibility as a high priority. To simply put this, an MBX or a WOR > that was created with an older version of MIPro should open in newer > versions of MIPro as is, no extra work needed. As of today, we don't > know of any instances where backwards compatibility was not supported. > If one finds such a case, we will regard it as a bug. > > As for older versions of MIPro opening new workspaces, a quick way to > see the oldest version a workspace can be opened in is by opening the > WOR file in a text editor like Notepad and looking at the second line > called !Version. That will list the oldest version of MIPro the > workspace can be read in. > > MapBasic: We have no plans to bundle MapBasic with MapInfo Professional. > Customers that are interested in simple MapBasic scripting can do this > by pasting MapBasic code in a workspace or in the MapBasic window. That > is why we bundle the MapBasic Reference Guide PDF with the MapInfo CD. > If one on the other hand wants to build UI enhancements and complex > automated routines then they will need to purchase the product. Users > that have been with us for some time now, know that we ensure that all > the major features we add to the product are exposed via MapBasic this > provides the flexibility users are requesting and the robustness we > demand from our product. > > > Thank you for your support, > > ___________________________________ > Moshe Binyamin > Product Manager > MapInfo Corporation > > > > _______________________________________________________________________ > List hosting provided by Directions Magazine | www.directionsmag.com | > To unsubscribe, send e-mail to [EMAIL PROTECTED] and put > "unsubscribe MapInfo-L" in the message body. > > > > _______________________________________________________________________ > List hosting provided by Directions Magazine | www.directionsmag.com | > To unsubscribe, send e-mail to [EMAIL PROTECTED] and > put "unsubscribe MapInfo-L" in the message body. _______________________________________________________________________ List hosting provided by Directions Magazine | www.directionsmag.com | To unsubscribe, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MapInfo-L" in the message body.
