Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
WININET.DLL Function Problem
Message
General information
Forum:
Visual FoxPro
Category:
Windows API functions
Miscellaneous
Thread ID:
00142611
Message ID:
00143123
Views:
34
>That explains some of my results; thanks, Rick. I can understand why the API call mis-IDs the connection type if I'm providing DNS inside the Proxy Server, but I don't understand the misqueues in status with AutoDialing enabled and dialing in progress or failed due to busy signals. Any clues other than 'the API wrappers are flaky'? Do the RAS functions like RASGetConnectStatus() return the detail properly in the RASCONNSTATUS structure? If so, and the connection details, other than a live connection exists, are needed, would it be better to use RasEnumConnections() to get a handle, and then examine the RASCONNSTATUS structure from RASGetConnectStatus()?

The RAS APIs aren't the problem - they should work fine. It's the WinInet
wrappers. I have briefly played with those a while back and they just didn't
work right. I tried both my own VFP implementations, some C++ code and some
SDK samples I downloaded. None reported the right connection status. It's
also been mentioned in some MIND articles...

Also, I don't think RAS is the right way to handle this. What if you
have a network connection to the Internet? No RAS, no connection handle
to check...

+++ Rick ---
+++ Rick ---

West Wind Technologies
Maui, Hawaii

west-wind.com/
West Wind Message Board
Rick's Web Log
Markdown Monster
---
Making waves on the Web

Where do you want to surf today?
Previous
Reply
Map
View

Click here to load this message in the networking platform