Hi John,


Yes, there are issues regarding MTS scalability but the way VFP lend its support to MTS is half-baked and this does not bode well with developer like some of use who wants to integrate with IIS, ADO and MTS. The other aspect of VFP is the IDE interface which is the only product in the Visual Studio suite that still sports the old look.

I am sorry for backtracking on the VFP survival issue but it looks like MS is not serious with their effort to push VFP as one of the programming language of choice. Personally I still find VFP a good data-centric language, better OOP support than VB and has one of the most feature-rich string function. I hope that MS could lend more support to the VFP product and make it on par with VB in terms of inter-operability with other MS products. Thanks.

Regards,
Kueh.


>I seen Rick got back to you. I am at the LA Fox conference now and am just catching up on messages....
>
>As Rick pointed out - the scaleability issues relate to calls to the same server (DLL) each DLL gets its own version of the runtime. Hence, another thread of execution gets spawned. Within each thread - VFP only supports 1 active apartment at a time. VB on the other hand - has the ability to process multiple apartments at a time. MTS is definitely in its infancy. For the vast majority of VFP applications written today, MTS is not a requirement and in many cases - should be avoided for the reaons Rick pointed out.
>
>One benefit of MTS that Rick did not point out is its role-based security model. You can define permissions in MTS - independent of your application. This is a nice feature. Once again however, the scaleability issues are still going to come into play.
>
>
>
>>Hi John,
>>
>>Is it possible for you to elaborate on the scaleablitiy issues with VFP6 on MTS ?. I need to be able to make a decision on the approach towards a new project that needs database access via the web. Thanks.
>>
>>Regards,
>>Kueh
>>
>>
>>>Hi Kim...
>>>
>>>If you need to pass data accross different processes - ADO is the way to go. This includes passing data to and from VFP components. As for MTS, there are some scaleability issues with VFP servers at this time. Depending on you application design, you may not need to resort to MTS. In short, if you can avoid using MTS with VFP in a web situation - do so.
>>>
>>>Finally, as Craig said - there is no one best solution. It depends on your own situation.
>>>
>>>
>>>>Hi,
>>>>
>>>>I would like to know which is the best approach to develop data access, ODBC or ADO in MTS. What are the pro and cons of each of the approaches ? Thanks.
>>>>
>>>>Regards,
>>>>Kueh.