I have an Access application where some users may require integration with QuickBooks and others do not use that feature. QuickBooks has a dll library for some of the vba programming statements.
The issue is that if the user does not have QuickBooks installed, the dll does not exist so the program fails on statements that require that dll for their definition.
I am familiar with the concept of conditional compiler statements -- i.e.
#If true statement then
<code>
#Else
<different code>
#Endif
However, I need to first test to see if the dll (QBFC13.dll) exists. I know how to write that piece of code. But when the entire application is attempted to be compiled, it naturally fails because the code is attempting to interpret commands that are supported by the dll. So this is a chicken/egg situation. I need some advice on how to approach this problem.
The issue is that if the user does not have QuickBooks installed, the dll does not exist so the program fails on statements that require that dll for their definition.
I am familiar with the concept of conditional compiler statements -- i.e.
#If true statement then
<code>
#Else
<different code>
#Endif
However, I need to first test to see if the dll (QBFC13.dll) exists. I know how to write that piece of code. But when the entire application is attempted to be compiled, it naturally fails because the code is attempting to interpret commands that are supported by the dll. So this is a chicken/egg situation. I need some advice on how to approach this problem.
