P
Peter
I have an Excel Add-in that now needs to open an Access database that has
user level security applied to it.
The only way I have been able to achieve this so far is using the VBA Shell
function, since by doing this I can pass the workgroup path and user
name/password to the DB.
Problem then of course is that I can't set a reference to the DB until
Access has started sufficiently to begin supporting OLE and the amount of
time this might take is indeterminate.
A very crude workaround I am using at the moment is to pause the Excel VBA
execution using Wait for a few seconds or so after calling the Shell
function, but even with this included, it still has a less than perfect
success rate.
Does anyone know how I can either pass workgroup and user parameters
thorough regular VBA such as OpenCurrentDatabase - or - monitor the process
handle of Access to see when it has fully initialised?
user level security applied to it.
The only way I have been able to achieve this so far is using the VBA Shell
function, since by doing this I can pass the workgroup path and user
name/password to the DB.
Problem then of course is that I can't set a reference to the DB until
Access has started sufficiently to begin supporting OLE and the amount of
time this might take is indeterminate.
A very crude workaround I am using at the moment is to pause the Excel VBA
execution using Wait for a few seconds or so after calling the Shell
function, but even with this included, it still has a less than perfect
success rate.
Does anyone know how I can either pass workgroup and user parameters
thorough regular VBA such as OpenCurrentDatabase - or - monitor the process
handle of Access to see when it has fully initialised?