While my company embarks on a project to change to Bentley Map, our legacy PowerMap V8 version needs updating quickly to the V8i SS1 version for Windows 7 compatibility, to get those users off Windows XP.
I have migrated most of the Workspace but encountered an issue where the Key-In "attach maps" does not exist in the v8i version, MAPMAN replaced with GEOMAPMAN.
Is there any way to replicate the key-in so I do not have to develop new configurations and MVBA/Macros?
cweber said:There is no simple solution
Hmmm ... yes ... but it's not so bad. What complicates the situation a bit is you are upgrading from "very very obsolete" to "obsolete". I don't recall exactly how PowerMap V8i SS1 map management differs from the old one, but I see three different possible general approaches:
Migrate your workspaces and customization to work with new map management: I am aware it sounds like exactly what you probably don't prefer to do and I also don't know how complex your customization using old attach map key-in is. What I see as benefits is you have to modify your configurations and macros (I guess MVBA), which is easy and no other tools are required. It's also an investment for future and you can be pretty sure what works in SS1 will work in any V8i version. Threat here can be if the new map manager doesn't offer the same functionality as the old one.
Implement own attach map key-in: Because the key-in doesn't exist anymore in PowerMap V8i SS1, you can replace the missing functionality seamlessly, so there will be no difference visible from a users perspective. But it's more complex task PowerMap V8i SS1 is locked product, so I guess you should use only plain obsolete MDL C and to compile the code to pseudo-code .ma file to be able to run it without password. Or you can ask for unlocking password and to compile it to native code.
Implement old attach map functionality using own MVBA macro and to call this macro from your other tools. MVBA cannot implement own key-ins, but it's not necessarily a big issue. VBA API is available (xft), but I am not sure if it's enough for your purposes (which is a threat of this approach).
cweber said:It is possible to call C functions from VBA.
Yes, but not always. There are VBA wrappers prepared for many MicroStation MDL functions, but I think there are no wrappers for Bentley Map C API. I hope Jeff or somebody else from geo team is able to answer it.
Without knowing too much about your environment, personaly I vote for the first way, to try to migrate to the new map manager functionality.
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
Jan Slegr said:What complicates the situation a bit is you are upgrading from "very very obsolete" to "obsolete"
It's not clear from the Bentley website that PowerMap is obsolete...
Bentley PowerMap offers similar functionality to Bentley Map. Bentley PowerMap is an easy-to-use GIS. It is highly customizable and uses the same XML Feature Modeling (XFM) platform as Bentley Map
However, when I look at the SELECT CD page, I see that PowerMap was last updated in 2009. How would a potential customer know that PowerMap is obsolete and that Bentley Map is today's bees knees?
Regards, Jon Summers LA Solutions
Sebastien.Lefrancois said:Bentley Map editions exist as Bentley Map PowerView, Bentley Map (For MicroStation and Standalone), Bentley Map Enterprise
Thanks for the hint! I found this Bentley Systems page that describes those editions, plus Bentley Map Mobile.