So, without my eyes burning holes, what difference do you get?
LizR
Posting Virtuoso
1,791 posts since Aug 2008
Reputation Points: 196
Solved Threads: 190
Do remember not all of us are in your timezone, and do have to sleep from time to time..
OK, looking at the code the first thing to do would be to check your winsock data arrival procedure is actually being called, and if so, what data you get.
Data doesnt always arrive as 1 chunk, which doesnt seem tobe accounted for in that proceedure overly well. In that the data could be split over a packet.
As long as the routine is being called you'll be able to track down why its not working - why you're moving to a language (eg vb for win32) which was dropped by MS.. im unsure, but, its your call.
You'll need to tell us if the data is returning the way you'd expect it to.
The other thing would be you've told the code to run in the onload not a button press so it snot goign to run on demand.
LizR
Posting Virtuoso
1,791 posts since Aug 2008
Reputation Points: 196
Solved Threads: 190
Put a break point in, add a watch to th value.. basic stuff.. thats how you tell whats in it.
LizR
Posting Virtuoso
1,791 posts since Aug 2008
Reputation Points: 196
Solved Threads: 190
which one does it get stuck in?
Only thing I can think of is
"#$0D#$0A" + "#$0D#$0A"
by putting in the " marks you're turning them to strings.. which isnt what you want. so its possibly not returning the data you want.
LizR
Posting Virtuoso
1,791 posts since Aug 2008
Reputation Points: 196
Solved Threads: 190
thats because vb doesnt do the #$ notation.. I believe its something like vbCrLf .. but I dont do vb, its pointless.
and I believe VB still has a pos function where you can test if its > 1 or not.. check the helpfile
LizR
Posting Virtuoso
1,791 posts since Aug 2008
Reputation Points: 196
Solved Threads: 190
Debugging is always the answer
Follow the data you get back, look at its values, look at what your code does.
I dont have vb6 to put it in. (or rather its around on a cd somewhere, but I am not loading it)
LizR
Posting Virtuoso
1,791 posts since Aug 2008
Reputation Points: 196
Solved Threads: 190
I still think simple debugging will highlight the problem quickly.
LizR
Posting Virtuoso
1,791 posts since Aug 2008
Reputation Points: 196
Solved Threads: 190
Put a break point on the first line in your data retrieval code
Add a watch to the value of the data returned eg buffer
Step through the code.
Most likely the issue is the value of buffer, if not, make a dummy app and play around with string functions till you find the one you want and how to use it
LizR
Posting Virtuoso
1,791 posts since Aug 2008
Reputation Points: 196
Solved Threads: 190
But you've been running it so, there shouldnt be syntax errors
LizR
Posting Virtuoso
1,791 posts since Aug 2008
Reputation Points: 196
Solved Threads: 190