This is my checklist for debugging Director-ASP communication

- The property names in the parameter list match the form variables
expected by the ASP page
- Set the data type explicitly to string
- Recheck the ASP code to make sure it is correct

Sometimes, especially when you're testing the ASP off a remote server,
there might be a communication problem that occurs. This is due to normal
network traffic. The best solution in such cases is to incorporate
appropriate error checks in Director. If you can post a sample of the error
that occurs, I guess it'd help determine the problem better.

Regards,
Pranav
-----------------------------------------------------------
"Simply stated, it is sagacious to eschew obfuscation."
--Norman Augustine



<snip>
netID = getNetText(getURL & "wayne.asp",["course_ID":course_ID,
"gameLevel":gameLevel])

I use the watcher window and see that director is sending the appropriate
values for each variable, but my client still wants to make sure we don't
have a variable leak coming from Director.

Can anyone explain to me what he might mean by a variable leak?  I know
about memory leaks, but as a middle of the class level programmer of lingo,

I am curious what this concept may be.



[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/lingo-l.cgi  To post messages to the list,
email [EMAIL PROTECTED]  (Problems, email [EMAIL PROTECTED])
Lingo-L is for learning and helping with programming Lingo.  Thanks!]

Reply via email to