Thanks a lot Heath, that solved the problem :-D

Thnks for the advice. I tried the new config u posted but its not working either. Anyhow, I've been looking around in the net and I'm not the only one who's come up with this problem. It's apparently a Net v1.1 issue due to new security features in remoting not implemented in v1.0. After searching for a while I've come up with two solutions: First one isn't any good: its using the Assembly AllowPartiallyTrustedCallers attribute in my Objects.dll where the DataCallContext object is. The code works this way but it shouldnt be the solution to my problem unless there is absolutely nothing else I could do. Second one is most probably the correct way to solve the problem: explictly change the server formatter's FilterLevel to 'Full'. (defualts to 'Low'). ...so, in case anybody else has this problem and stumbles upon this post while searching the forum, the problem will be fixed if they configure the server remoting config file similar to the following: Thanks for all the help.

Ok Javier, got it! :D I've discoverd one hell of a class in the Reflexion namespace that has solved all my problems: TypeDelegator public object RunMethod(string methodName, object[] arguments) { object proxy=GetProxy(); TypeDelegator delegator=new TypeDelegator(typeof(IDataLayerTool)); return delegator.GetMethod(methodName).Invoke(proxy,arguments); } It seems that the TypeDelegator can map correctly through interfaces and even makes the job a lot easier as u dont have to create delegates as u would with a DynamicInvoke. Nice little class, yessir :D Again, thanks for your time Javier.

Thanks for the reply Fadee! glad to here there will be no problem. As a matter of fact, if I would have stopped to think about MDAC I wouldnt have wasted yout time :p... you are absolutely right, MDAC contains the drivers for all standard DB connectivity including Access.

Thanks for the input Alex. Yes, my remote object will be a single call object and wont need to be a client activated object with state info, so I wont have to worry about the objects lifespan. I'll register a client channel upon the client app's start and keep that one throughout it's whole life.

Its not possible to insert negative sign into double textbox. Maybe anybody knows how to correct double textbox control ?

bump...