>I have a general question on designing 3-tier application. I am refactoring an application which is design a monolithic (as defined by Kevin McNeish).
>
>Would it be right approach (in general) to have cursors passed between UI tier and biz tier? That is, my plan is to create a cursor for every table that has to be updated. Then populate the cursors in the UI tier and pass them to BIZ tier and update data tables from the cursors. Does it make sense?
>
>TIA.

I noticed you said you were using VFP6, it would be a wise choice to move to VFP7 or 8 if you want an easier ride, they have some nice features such as XML functions and event-binding.

There are loads of ways to implement a n-tier model, and it will be especially difficult if you haven't done it before. I would use XML to talk between layers, when your UI recieves XML, turn it into a cursor that will be bound to your controls, then post back any commits via XML too. Depending on the data-volume, this shouldn't slow the app down at all.

Also remember that if you can seperate a tier with almost no code re-factoring, then you're on the right track.

Good luck
Kev