I thought I would create cursors in UI tier and they would be "visible" in BIZ tier. Therefore, "passing" would not be necessary. I realize this is not "true" n-tier design. But at this stage I just want to separate UI from BIZ so that I don't have to repeat code in multiple forms (as I do now).

What you are doing is implementing a "logical" n-tier design that separates the UI from the business logic (and the data handling?) -- but will probably be compiled into one large app. There is nothing wrong with that at all.

The UI/Business Logic can use cursors only, but you may want to keep your data read/writes more generic so in the future you can use ADO/XML/ODBC without too much re-coding, just add more case statements to your data layer.

Kevin