AnsweredAssumed Answered

Excel VBA vs Processbook VBA

Question asked by andrew_Inwood on Jul 20, 2018
Latest reply on Jul 22, 2018 by andrew_Inwood

We use Processbook VBA extensively.  I am trying to write a generic VBA Class that can be used in both Excel and ProcessBook.  To make code maintenance easier, I really (really!) don't want to have two versions of the class, but that is my fallback plan if I need it.


It is generally fine - most of the objects I am working with are generic enough that I don't need to worry about the differences between the two versions (I'm dealing with text files and common controls, not Displays and WorkSheets).  But one issue I am stuck on:  I need to get the path of the current file.


in Excel, it's ActiveWorkbook.Path.  In ProcessBook, it's ThisDisplay.Path.


I was trying to see if there was something generic in the Application Object or some other property that could lead me to this answer, but can't find anything.  I could possibly late-bind an object based on the Application.Name, but not sure how to late bind in Processbook (can it be done?)


Any suggestions?