Run-time error '53':
File not found: myfilename.dll
It does this even though the dll file is quite definitely there.
A small program compiled with VB6 to do what VBA does behaves the same
way.
In the VB code if I change the name of the routine being called to a
name that is not in the dll, the same error message is displayed.
Something is messed up somewhere, but I just can't figure out what it
is!@#$%
Has anyone encountered this problem, and know how to solve it? I'm
desperate.
The problem can happen with either XP or Vista, and with either excel
2003 or excel 2007.
Thanks,
Brian
Regards,
Peter T
"Brian Murphy" <bmu...@xlrotor.com> wrote in message
news:4b4ba20e-6ed3-4d0c...@d4g2000yqa.googlegroups.com...
I think the problem might be some other file in the Windows directory
needs to be present, and it is on some systems but not all. I have
made other dll's that don't have this problem. I'm trying to figure
out if there is some linker option I need to turn on. So far I
haven't found anything. But the more I think about it, the more
convinced I am this is the answer.
Brian
sPath = "C:\<path>\"
sFile = "myApp.dll"
sOldDir = CurDir
ChDir sPath
On Error Resume Next
nAttr = GetAttr(sFile)
bFileExists = (Err.Number = 0) And ((nAttr And VBA.vbDirectory) = 0)
ChDir sOldDir
On Error GoTo 0
If bFileExists Then
' Call your dll function stuff here
Else
MsgBox sPath & sFile & vbCr & "not found"
End If
Regards,
Peter T
"Brian Murphy" <bmu...@xlrotor.com> wrote in message
news:f3e9531f-054e-4ea2...@m7g2000prd.googlegroups.com...
I'm pretty sure it's a compiler dependency thing?
I just posted my question on comp.lang.fortran
This particular newsgroup has more spam than fortran.
Which is a downright shame.
I wonder how the excel newsgroups avoid this?
Brian
So I hope to have this fixed later tonight.
Brian
http://groups.google.com.na/group/comp.lang.fortran/msg/d4ae6d5b2dcf8c42
The "file not found" error 53 was caused by some fortran-compiler-
specific dlls that were needed that I didn't know about. When I
eliminated that, the problem cleared up.
But also the very same error message is triggered if the upper/lower
case of the routine name doesn't match that in the dll.
Cheers,
Brian