Just a quick update: I changed my Http.ReceiveBytes() routine to accept a (void *) pointer rather than a (Char *) -- I do the conversion to a (Char *) inside that routine now, then do the receive from the socket, and it all appears to be working now.
Thank you for the assistance. > --- Jeff Loucks <[EMAIL PROTECTED]> wrote: > > > 1. I think you said you are allocating an > > intermediate buffer for > > debugging. Otherwise, you could call > > http_cl.ReceiveBytes() directly > > with pData and pSize. > > > > 2. I suggested checking the value of pData to see > if > > it is a > > reasonable value, but only while you are debugging > > the problem. > > Normally, you expect the value to be passed > > correctly, but if it > > isn't, then it could be a clue. > > > > 3. If you are certain that none of your routines > are > > corrupting memory > > by writing to incorrect locations, and that you > are > > faithfully > > communicating the contents of the prc to ExgMgr, > > then I can only > > assume there is a problem with ExgMgr. A problem > of > > this type with > > ExgMgr is unlikely, however. Can you use the > > debugger (or serial > > tracing) to step through the whole process? I > > suspect that at some > > point a write occurs to the wrong address, or the > > prc content gets > > confused. > > > > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam > protection around > http://mail.yahoo.com > > -- > For information on using the ACCESS Developer > Forums, or to unsubscribe, please see > http://www.access-company.com/developers/forums/ > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
