P
pbrase
I have an Access 2002 application that uses wininet.dll to access FTP. Ran
like a champ for well over a year and suddenly stopped working. After a great
deal of cursing and debugging, I found that the problem seemed to come from a
new version of wininet, with file date of Jan. 2007. If I swap that out with
an older version of wininet from Oct. 2006, the app works fine. Problem with
the new is that it can't connect to the target FTP site, that is, the call to
the InetOpen function always returns a 0 handle, although I can verify
through other applications that the FTP site is operating normally. I've
tried tweaking the InetOpen params, to no avail. I'm guessing this is some
sort of weird configuration issue since the problem doesn't seem to be
happening for anyone else. Any suggestions would be greatly appreciated.
like a champ for well over a year and suddenly stopped working. After a great
deal of cursing and debugging, I found that the problem seemed to come from a
new version of wininet, with file date of Jan. 2007. If I swap that out with
an older version of wininet from Oct. 2006, the app works fine. Problem with
the new is that it can't connect to the target FTP site, that is, the call to
the InetOpen function always returns a 0 handle, although I can verify
through other applications that the FTP site is operating normally. I've
tried tweaking the InetOpen params, to no avail. I'm guessing this is some
sort of weird configuration issue since the problem doesn't seem to be
happening for anyone else. Any suggestions would be greatly appreciated.