Hi,

My development laptop is behaving weird when it comes to returning variables 
via the getCargo method.

What is happening is that the getCargo method returns NIL most of the time 
and correctly for the rest.  Usually 2-3 times as NIL and then OK. Sitting 
there pressing F5 and refreshing the page until it works is most 
entertaining but not practical 

My setup is XP Pro running IIS and WAA v1.90.331.

Any one come across this problem before?

Regards

Jeremy

Jeremy Suiter wrote:

> What is happening is that the getCargo method returns NIL most of the time 
> and correctly for the rest.  Usually 2-3 times as NIL and then OK. Sitting 
> there pressing F5 and refreshing the page until it works is most 
> entertaining but not practical 

The values are stored in waa1srv.dbf/fpt/cdx in the same directory as
waa1srv.exe - try to delete these files first.

Also clear the browsers cookie cache.

You could also check what is going on between browser and server by using
the Fiddler debugging proxy ( http://www.fiddlertool.com ) - you can check
if the browser always sends the correkt cookie. 

The cokie value directly corresponds to the "session" field in waa1srv.dbf

HTH & regards
thomas

Thomas

I've already tried deleting the .dbf and clearing to cookie files with no 
effect.

I've just installed fiddler and it looks good.  I'll have a look and see if 
I can spot what is happening.

Thanks

Jeremy

"Thomas Braun" <spam@software-braun.de> wrote in message 
news:tdyq5dj640c4$.1dvygb1hcpn7q$.dlg@40tude.net...
> Jeremy Suiter wrote:
>
>> What is happening is that the getCargo method returns NIL most of the 
>> time
>> and correctly for the rest.  Usually 2-3 times as NIL and then OK. 
>> Sitting
>> there pressing F5 and refreshing the page until it works is most
>> entertaining but not practical 
>
> The values are stored in waa1srv.dbf/fpt/cdx in the same directory as
> waa1srv.exe - try to delete these files first.
>
> Also clear the browsers cookie cache.
>
> You could also check what is going on between browser and server by using
> the Fiddler debugging proxy ( http://www.fiddlertool.com ) - you can check
> if the browser always sends the correkt cookie.
>
> The cokie value directly corresponds to the "session" field in waa1srv.dbf
>
> HTH & regards
> thomas