I seem to remember reading somewhere that, if you do not include the .dll
path name in the VBA 'Declare Function' statement, Windows looks in the
following places for .dlls (in this particular order):
1)The MS Access executable directory
2)The current directory (i.e. the same dir as the .mdb)
3)windows\system32
4)other places... (maybe looks at the "path=" enviroment variable?)
Firstly, is this right?
If so, why is Access failing to find the .dll even though it is in the same
dir as the .mdb (case 2 above)?
If I move the .dll to windows\system32, it finds it no problem. If I specify
a path (e.g.:
Declare Sub xyzdll Lib "c:\foo\xyz.dll"
it works no problem.
But if I just leave it sitting in the same dir as the .mdb:
"Run time error '53': File not found"
I'm (pretty) sure that this used to work.
Any suggestions?
TIA
PS: Running MSAccess XP
--
Scott
Xbox Live Gamertag: scottmorrison
Xbox Live Games: Top Spin, PGR2, RS3, RTCW, CounterStrike, Tetris