Hiya John ---

Look at the excellent knowledge base articles posted two days ago by Jim Booth --- one of them specifically deals with middle-tier objects.

I have written business rules objects that were separate DLLs but have shied away from DLL data objects. Due to the fact that you lose native grid capabilities I haven't done any production work with unbound controls (but experimented a lot). John Peterson has a solution for using ADO and containering ActiveX grids.

In summary, though, planning dictates how much work/add'l coding there's going to be. If you plan from the beginning n-tier and mold your framework towards that goal, then I find no more coding is really involved just *different* coding.


>Just curious before I setforth on my n-tier journey, how much more work, in your opinion, was/is needed in your projects? I know there's more coding involved since word "bound" (e.g. controls) becomes somewhat meaningless. In addition, have you tried physically separating the UI from BO (separate EXE/DLL), and if so, what is your experience?