Upstream??

[ev]

i have the same problem.
i always need to do
conn.services(replyObject, data)
and then
var replyObject=new Object()
replyObject.onResult=function(result){
//codehere
}
if i do the _Result functions, the function wont execute.
ev

[Louis Simpson]

Yeah because your php script is expecting one argument and you are passing two.

What if you leave it at.
[script]
function addClient_Result(result) {
  trace ("Result = " + result);
}
function addClient() {
  var newClient = new Object();
  newClient.companyName = CompanyName;
  newClient.businessType = BusinessType;
  newClient.contactName = ContactName;
  newClient.Position = Position;
  newClient.phoneNumberAC = PhoneNumberAC;
  newClient.phoneNumber = PhoneNumber;
  newClient.faxNumberAC = FaxNumberAC;
  newClient.faxNumber = FaxNumber;
  newClient.email = Email;
  newClient.postalAddress = PostalAddress;
  newClient.city = City;
  newClient.state = State;
  newClient.country = Country;
  newClient.postcode = Postcode;
  newClient.streetAddress = StreetAddress;
  newClient.sCity = SCity;
  newClient.sState = SState;
  newClient.sCountry = SCountry;
  newClient.sPostCode = SPostCode;
  newClient.Url = Url;
  newClient.cdrom = CDROM;
  newClient.interest = Interest;
  trace("sent request. newClient: " + newClient.toString());
  scdbservice.addClient(newClient);
  }
}
[/script]

[mrluke]

Mine actually receives the addClient_Result(result) - Visible in the NetDebugger - Just will not execute the tasks in the function

[Script]

function addClient_Result(result) {
//doesn't do any thing here  
trace ("Result = " + result);
}
[/Script]

But when the default responder is added, SWEET, everything works.

Luke

[ev]

ok, i see how ur doing it louis...
then as i see it, using the _Result handlers is only an efficient option when sending [large amounts] of data and recieving a result back.
if ur only sending a simple argument, one which doesn't need to be constructed over a long amount of code (like an object or recordset object), then ur better off defining the result as a seperate object within the function that calls the service.  otherwise it just seems to me like cluttering your code.
but i can see why it would be good practice when something lengthy needs to be constructed and then sent to the server.
ev