The best way to see what's going on would be to use a logging mechanism to see what's actually being reported. There are two main ways to do this; one is to write the data to stndout which you can read in the Console application. The other is to just put a temporary field on the card that will record everything that's happening. I wouldn't use "answer" because that blocks all messages until you dismiss the dialog.
If you use a temp field, then do something like this:
Code: Select all
on urlProgress pURL,pStatus
put pStatus & cr after fld "temp"
end urlProgress
That will show you everything that's being sent back as the file uploads. It should give you information about what's going wrong.
You can also write to stndout like this if you prefer:
Code: Select all
on urlProgress pURL,pStatus
put pStatus & cr
end urlProgress
This will send the results to Console and doesn't require you to create a field, but it will only work in the simulator. To see what's happening, open the Console app while your stack is running in the simulator. Put your stack name into the filter field so you will only see messages that come from your stack. Then run your upload handler and watch the progress in the Console.
The urlProgress message is a system message that is activated automatically by the engine whenever an upload or download occurs. You don't need to do anything to trigger it, it's just another event the engine notifies you about.
