Hello,
I am using Power Geopak V8i SS2.
I am working with NCDOT for the first time and downloaded their workspace. I have gotten the NCDOT workspace to function with Power Geopak V8i SS2 (NCDOT is standardized on Geopak V8i SS2 only). However, their Geotechnical workspace is giving me the attached Macro Alert. Any suggestions how to resolve this alert?
you would need to look at that ucf file and see what is loading and whether the paths are correct. probably just need to change the name to powergeopak on the path
For more information about the Road and Site design tools, visit the Road and Site design WIKI at: http://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki
I have compared a functioning (Roadway.ucf) to the one giving issues (Geotechnical.ucf) and they are exactly the same, line by line. I used the "-debug" to search for "not found" macros and there were a few. I found _USTN_PROJECTCFG the only "not found" item common to the Geotechnical.ucf. However, a closer inspection shows this path to be set; not sure what to do with this. The subject of Geopak versus Power Geopak; I only see Power Geopak in the debug file, however there must be a 1000 occurrences at least, the Geotechnical user file has no reference to Geopak. Due to time with project deadlines and production concerns, Is there a better way to determine which specific Macro source is not being found?
I believe it is more on an informational message than a critical error. And is from a MicroStation Basic macro which was compiled into a .ba file and there is no longer a copy of its .bas file (source). Many DOT workspaces use MicroStation Basic macros to automate simple, repetitive tasks and somewhere in its workspace it is trying to run this - automatically if this always appears, or during some application step, if it appears only under certain workflows.
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration
CADDCOP,
I did change from Geopak to Power Geopak recently and it may be an issue with the Microstation not being external. Is there a way to determine which Microstation Basic file the program is looking for?
That might require some real detective work. the -debug output (msdebug.txt) can show you every variable that loads and the order they load. Some are to define an autorun VBA, others can define an autorun MDL. I don't believe they ever made one to autorun a.ba file - but they did make an MDL that when autorun could do that.
It might have been called runmacro.ma. Searching the debug files and the MDL and Macro Folder of the workspace might also provide clues.
A lot of this is coming from memory, so I can't offer much depth. But a search of the newsgroups might also help, even it the threads are old or archived.
So it sounds like every *.ba file must also have its associated *.bas file. If there is a missing *.bas then that would be the culprit?
I noticed in the message center a MACRO_SORTBYNU unloaded and MACRO_SORTBYNU loaded. I found the macro and it is SortByNumber.ba. I assume the SortByNumber.bas file is required for this macro to run properly. So I should try to get the file with "bas" extension (source file) or is there another way to get the macro to load properly and eliminate the alert message?
So apparently, the "bas" extension is not a required file for the macro to function properly, has nothing to do with it. But having the macro file in the path that the configuration path is set to, is required. The SortByNumber.ba macro was in a Roadway workspace but the Primary Search Path for the macros was the Geotechnical and DOT_Stds. Once I copied the SortByNumber.ba macro to the DOT_Stds directory, the alert message did not occur. Can you confirm if my understanding above is correct?