>Kevin,
>
>If I remember correctly, at Devcon, you showed how a MM Business Object can serve data in different flavors (vfp cursor, ado, xml or something like that) by setting a property of the Business Object.
>
>How will that type of thing work work in a COM/MTS environment? Does that business object you instantiate imply some sort of STATE?
>
>I thought that in a stateless environment, like if I were to use WebConnect, you would have to call some method, pass a parameter as to the type of data you want and it passes it back.
>
>Thanks for any insight in helping me understand this concept,
>Ed Lennon
>SUI

I don't know how Kevin is going to address this in the new version, but I can tell you how it works currently. In it's current incarnation, you would need to set the return type property before you compile your DLL. Under WebConnect, the state "problem" really isn't an issue. While you're using the business object you don't have to worry about any context switches. That is, the object maintains state while you're using it. While each hit that a user makes isn't guaranteed to be the same object, you can be assured that inside your Process method's you're using the same bizobj. MTS has some options to allow you to maintain a context state while you're using your objects. Of course, you give up some of the performance benefits by doing that. Ideally, you wouldn't want to do that.