We had some issues with this VBA previously and this is the solution we came up with.

Drainage Tabulation VBA Error

• Issue
  • Compile Error: Cannot find project or library
• Cause
  • The VBA has the wrong location for the Excel installation
    • The VBA looks for the 32bit version of Excel
    • If the 64bit version is installed, this error will occur
• Solution
  • Stop the VBA from running
  • Tools -> References
    • Set the reference looking for EXCEL to C:\Program Files\Microsoft Office\root\Office16
  • Close Microstation
  • Save the VBA with the same name and overwrite.

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.  

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.