Hey Francis, at some point I think I did have a server-side property called "code" but I changed that soon after I created it.I'm sure I have nothing with that name now. I've either deleted or changed the name of it.I think you're right - there's persisting here. Do you use WebOrb too?

STILL NOT FIXED!!! I must have tried the app 20 times after making the changes but the problem has come back.Back to the drawing board.

Hey Greg, thanks for the response.I'm still not sure where the property "code" is. I've searched through my entire project and the server-side methods too. I guess it could be something that WebOrb returns as an error message.Anyway, I found the root cause of the problem. I was calling the same server-side method twice, sometimes I guess due to slightly different timings within the app, it would work, and sometimes not.After Googling and finding a couple of mentions of changing properties from p...

I figured this out out in the end. I needed to put a crossdomain.xml policy file into the root of my WebOrb site allowing access to the site that hosted my app.

OK, I have some more information. Cutting the IIS server out of the equation...If I launch the app from bin-debug, it works.If l launch the app from bin-release, data functionality does not work.If I copy the bin-debug folder to a new location on my PC, data functionality does not work.This suggests to me that (a) the files in bin-debug are using hard-coded paths and (b) the release is not being built properly.Any more ideas on why I'm losing data connectivity when creating the release build?

Thanks for the reply Greg but unfortunately it hasn't fixed it. I did notice that the -use-network=true option resulted in my assets and css being separated out into seprate files.