No worries, all help appreciated. The world makes sense again and I can enjoy my weekend .Thanks again for the help!~e

I think I stumbled on a soltuotion:from: http://flexdiary.blogspot.com/2008/11/thoughts-on-remoting.html"I think the real reason the serialization wasn't working was the last thing I discovered, which is that you have to have a dummy variable typed as your custom class in the same class as the Remot...

Thanks for looking at the code.The import(s) weren't required for the other example ( since the first example didn't need to use a List or ArrayList ), so that's ok.According to the Adobe docs, all you need to ensure the RO and VO match up is the same # of properties, and the same property names ( c...

Hey Michael, this code works:BTW - I changed Flex package path to match that on server.Flex VO======package com.mypackage.admin.vo{    import mx.collections.ArrayCollection;        [RemoteClass(alias="com.mypackage.admin.vo.BrandVO")]    public class BrandVO    {        public var brandId:int;      ...

Thanks again for the feedback.I tried what you suggested and still have the same problem.Plus the other VO's follow the same convention and they seem to corrolate to the ROs w/o a prob.Very strange.~e

Hey Michael,Thank you for the quick response and helpful suggestion.Sure enough, if I just call for a CaseVO, it still is generically typed as an Object; so your theory that Flex cannot match up the RO and VO seems to be the correct. I have reviewed the code however and can't see any discrepancies. ...

I have a Flex 3 app which uses remoting. All works relatively well except for the following...I have a deeply nested object graph as follows:( btw: each VO uses [RemoteClass(alias="com.mypackage.xxx")] meta tags )The main class is called "BrandVO" which contains an ArrayCollection on ProductLineVOs....