>>>>>>>>>>>>>>>>>>>
>>Doesn't almost seem like an ADO COM could marshal data for a variety of clients thick (VFP, VB, etc), thin (Browser/ASP) from a variety of backends SQL/FOXDBC,Access?
>>>>>>>>>>>>>>>>>>>
>>
>>Sure, if it's properly written using an N-Tier architecture.
>Wouldn't you agree it would be fairly difficult to implement improperly written n-tier objects. ARe there conventions for the 'n' in n-tier. I mean when:
>n=1 is that a client call to connect?
>n=2 is that a server side client connection object?
>n=3 is that a backend, like sql, etc?
>What does 'N' mean?
>Regards
>Terry

---

N=3 usually where it's not a standalone FP app anymore.
1= Client && VFP, VB, Excell, Delphi Just forms and reports
2= BizObjects && VFP, VB, Delphi All data rules and responsiblites
3= Data Base && Just the data

__Stephen