|
|||||||
![]() |
|
|
Thread Tools | Search this Thread | Display Modes |
|
#1
|
|||
|
|||
|
I have an existing ACCESS 97 application with WININET HTTP functions (IE
6.0.2800.1106) which have stopped working with the move of the application to ACCESS 2003, under Windows XP using IE 6.2900.2180. There is nothing is being processed by the ASP which receives the HttpSendRequest. I have put DEBUG.PRINT statements in my ACCESS WININET module to help me understand what is happening to the HTTP calls. I have run in both environments and compared the results. The one difference I can see is on the HttpQueryInfo return. I have made the QueryInfo call using Content_Length, Status_Code and Status_Denied. On my working application I always get a Status code return of 200 (OK). But on the failing application I always get a return of zero. I cannot find this zero status code in the reference material on WININET, which I have consulted to help resolve this problem, so I am stuck. I am a beginner at Internet programming and have inherited this application from someone who has now left our company. Has anyone out there got any advice for me |
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Re: Ineternet Explorer Stops Working! | Andy | Windows Update | 6 | 01-05-2006 05:04 PM |
| Re: Ineternet Explorer Stops Working! | PA Bear | Windows Update | 0 | 01-05-2006 05:01 PM |
| Monitor Stops Working after Remote Desktop Session | Venkat V | Windows XP Work Remotely | 2 | 01-05-2006 07:15 AM |
| When I connect to internet the computer stops working | rpasquel31 | Windows XP Network Web | 5 | 01-05-2006 04:09 AM |