Converting UCM Macros to Basic

Question

For Microstation V8i, I have been given the assignment of converting several UCMs to Basic or Visual Basic. Since there is a manual for converting UCM to Basic, I decided that I would convert them to Basic. Then new macros could be created in VBA. I am just learning Microstation and of course, my management wants this assignment completed quickly. 
 I would like to know if it is possible to call a Basic Macro from another Basic Macro with parameters of any built-in or Macrostation type, such as an MbePoint. If not, is there an alternative? These small UCM Macros that are called frequently by many Macros, but I don't think there are include files in Basic. 
 For now, I'm using Basic Subroutines, which isn't ideal. 
 I would like to convert the UCMs to VBA, but I think that would take much longer, unfortunately.

Robert Hook · Answer

Elaine, the process you are describing is what I consider to be a typical "Migration Project". There are several options and considerations in the process that should be evaluated before being able to project how long your migration project will take. 
 Here are some considerations: 
 How has the Product changed? In your case MicroStation SE (5.7) to MicroStation V8i 8.11 has change drastically in capabiities and workflows. These points are fundamental in your approach. 
 MicroStation V7 had 63 levels and the V7 design file format. MicroStation V8 has a new format, capabilities, workflows, and nearly limitless levels, models, styles (line, text, dimension), etc. For one, your UCM unless the most simple will not work in MicroStation V8. MicroStation BASIC being older also has the similar limitations and both would require several and/or extreme hacks to accomplish something that a more modern MicroStation VBA could handle with ease. MicroStation VBA has its (smaller) set of limitations, but can be augmented with MicroStation MDL (C/C++ programming language APIs) to enhance VBA, or offer functionality in a stand-alone manner. 
 The first part of such a daunting task is to ask some of these questions from the CAD admin/operators: 
 1. How many programs are there? 
 2. What do they do? 
 3. Does the Product NOW offer this functionality? 
 4. Have the workflows in the product changed making the older way ineffecient or obsolete? 
 5. How many programs do we need to migrate? 
 6. Do we only need to migrate some or all the code/featurs of the customization forward? 
 7. What programming language(s) are required? 
 8. Do I have the experience necessary to perform some or all the work defined as being required? 
 9. Can I meet the projected deadlines? 
 10. Will I have adequate time to test each app, feature, and (new) workflow and validate everthing is working? 
 There are more considerations along the way, but these steps above are generic and apply to any software product that provides customization/programming options. 
 I would recommend to evaluate the existing functionality and find it, or find out how to accomplish it in the new product. Use MicroStation VBA since it is relatively easy to learn and prototype functionality quickly. TIP: Plenty of sample code in the VBA Help document - Alt F11, F2 (object browser), Search for something - e.g. Cell, then hilite an item displayed in the results and Press F1 - noting "Example" hyperlinks for sample code. Lastly, if the deadline(s) are imperative I would recomend that you consider contacting our Bentley Profession Services group since they are already fully equipped to handle and meet your customization needs. Here is some contact information for convenience. 
 Bentley Professional Services (BPS) - For Bentley product customization services 
 Web: www.bentley.com/.../Bentley+Professional+Services 
 E-mail: bentley.consulting@bentley.com 
 Wish you the best in your efforts and please make sure to use the Be Communities to help you find your way and help with any specific programming questions you may have. 
 HTH, 
 Bob