>A VCX DCOM with the following properties and triggers:
>1) An account_number property (receives the account number from client form).
>2) An account_number_assign method (triggers a seek on the account_number to the DNS Account/Name DBF/CDX)
>3) A return_name property (recieves the name resulting from the account_number_assign method)
>4) A return_name_assign method (triggers a "forward" of the DCOM return_name contents to the Client name text box.)
I'm not quite sure I understand exactly what you are doing, but I have a suggestion or tow for implementing this server object:
Instead of having a property to set that holds the account number between calls, you should consider passing the account number in a GetName() method, so you only have to make a single call to the server object. This goes along the stateless object design theory that says the object should get everything it needs to know to operate from a single method call. A design like this will help your object scale better, and work better within MTS.
Erik Moore
Clientelligence