I receiving the attached error when running the Drainage Tabulation tool from the menu bar. I have a drainage project open and the GEOPAK gpk path as well as working directory path are pointed to the drainage folder. The GPK and GDF files are in the drainage folder. The GDF file opens fine and the network can be analyzed OK.
Using PowerGEOPAK 08.11.09.878 and FDOT SS4 MR9.
Thanks
Sean Keene
We had some issues with this VBA previously and this is the solution we came up with.
Zachary Billings, P.E.
Senior Roadway Engineer (Licensed in FL and MI)
CONSOR Engineers, LLC
System Info:
Windows 10 | Intel Core i7-9700k | Nvidia RTX 3080 FTW3 Ultra | 32 GB of RAM | 500 GB Samsung 960 EVO NVME
Power GEOPAK V8i Select Series 10 Version 08.11.09.918 | FDOT SS10 Version 01.04.01
ORD Version 10.09.00.91 | FDOT Connect Version 10.09.00.00
YouTube Page for ORD: https://www.youtube.com/channel/UC3S-94f7_yUJ-GMhMYPhInA
Hey Zach, we can't change the VBA - shows password protected.
If you open the MicroStation VBA Project Manager first (from MicroStation menu Utilities->Macro->Project Manager) and then load the Draintab.mvba into the VBA Project Manager you can then open the Draintab.mvba via the Visual Basic Editor. Once the VBA editor is open you can then add the path to EXCEL.exe on your computers. Please be sure to make a backup of the Draintab.mvba first before editing.
Thanks Sean, We figured out the issue was not within the VBA or Excel version. The user apparently was attempting to load the former SS4 FDOT smd file in Geopak SS10 preferences.
Any idea why this would happen on systems that only run 32bit office?
UPDATE:
I’ve identified this issue we’re having with the Drainage Tabulation VBA. Our lead drainage expert has several GDF files for a particular project. They are careful to keep only one GDF in the Drainage directory at a given time. Essentially, the VBA error boils down to the single Spread Tab Settings File (*.SPS) the VBA attempts to use for any loaded GDF files. If the VBA sees a different GDF in its settings file than what is the “active network” it crashes Geopak Drainage. When loading the desired GDF into the VBA dialog its “Report Network” dropdown would throw the VBA error. Once a new SPS file is created (save-as with the path to the correct GDF), we can close and relaunch the VBA and the Report Network dropdown works without error. This appears to be required (load-reload for all new GDF files). Weird behavior, but this VBA may need adjustment for any projects attempting to use more than one GDF for different areas of the project.