all groups > macromedia flash flash remoting > february 2005 >
You're in the

macromedia flash flash remoting

group:

Weird Error on Netservices include



Weird Error on Netservices include phil ashby
2/7/2005 1:12:12 PM
macromedia flash flash remoting: OK,

have an app that was built using AS1 in MX that uses the standard db connect
blurb (below)

// Include the Required NetService class files
#include "NetDebug.as"
#include "NetServices.as"
// connect to the Flash Remoting service provider
if (isGatewayOpen == null)
{
// do this code only once
isGatewayOpen = true;
// Make the Gateway connection
NetServices.setDefaultGatewayUrl ("http://myserver/flashservices/gateway");
gatewayConnnection = NetServices.createGatewayConnection ();
getremotedata = gatewayConnnection.getService
("mycomponentsfolder.mycomponentname", this);
trace ("connected");
}

I want to develop the app to use some AS2 components, but when I bring this
code into MXPro I get the following errors

**Error** C:\Documents and Settings\Phil_A\Local Settings\Application
Data\Macromedia\Flash MX 2004\en\Configuration\Include\NetServices.as: Line 80:
Expected a field name after '.' operator.
NetServices.trace("NetServices", "info", 2, func + " was received from
server: " + result.class + " " + result.description);

**Error** C:\Documents and Settings\Phil_A\Local Settings\Application
Data\Macromedia\Flash MX 2004\en\Configuration\Include\NetServices.as: Line 82:
Unexpected '}' encountered
}

Total ActionScript Errors: 2 Reported Errors: 2

BUT...my colleague has exactly the same setup as me - same version of Flash,
same files in the include folder - everything - and his works fine!? I even
copied his entire conguration folder over, but still get the same problem?!

when I strip everything out and just have the include Netservices.as I get the
same problem.

I even tried uninstalling and reinstalling....but nothing.

HELP!?

Phil
Re: Weird Error on Netservices include phil ashby
2/10/2005 10:46:17 AM
sorted this Did another unstall, but also deleted all the dross that the install leaves behind. Then did a reinstall into a virgin directory and hey presto, problem fixed.

AddThis Social Bookmark Button