Peter Thanks for the reply. Hmmm, at first glance it all seems a bit complicated (simpleton, remember :-), and the following factors: 1) I've already got my file conversions all set up and this would seem like "starting over from scratch" 2) Stops is not the only table - I have routes, zones, groups of zones, street segments (polylines), those making up routes, stops-routes m-m relnships, et al. 3) I've long ago been bitten with VFP-MI integration, and I decided not to go down the ODBC route 4) the steps you've outlined all seem a bit "manual", via MI and not MB, whereas I want to achieve all this programmatically. (When I referred to "manual" in my orig. Msg, I meant via my VFP app. Rathewr than graphically via the map).
In short, I'm not prepared for a major overhaul in my approach to this problem. There are other 2-way updates for other tables that I already have sorted out - this is just the last outstanding feature. What I was hoping for was a pointer to some MB procs/funcs that can convert the new E & N to the object's X & Y (I assumed that as the table was made mappable by creating the points - objs - from the existing lat/long (E & N) it would be reversible, in that a new X & Y in the obj could generate new E & N. Thanks awfully for your time - any other suggestions? Terry P.S. Lately I've been getting several repeated message from MI-L - yours came 3 times, plus, presumably, a "personal" reply, not via MI-L. --------------------------------------------------------------------- List hosting provided by Directions Magazine | www.directionsmag.com | To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Message number: 16731
