Charlie:
I didn't know that I couldn't pass a cursor from a COM. I'm experimenting with ADO & VFPCOM locally right now - they seem to work fine. I thought I was just about ready implement test DCOM's (.exe's) to be placed on the server.

I was hoping I didn't have to do any kind of database/table and/or calculation type routines on the GUI - located on the workstations.

Are you suggesting that I accept the recordsets from the COM, change it into a cursor, then manipulate the data in the GUI? This would force me to do calculation in the GUI also, wouldn't it? ... well maybe not.

By the way, do you know if a VFP COM can pass oRecorset to a VB application?

Thanks for you help Charlie

Mal


>Malcom:
>
>From what you are saying, it sounds like you are using vfp on the presentation layer as well. If this is what you want to do, you'll have to pass a recordset, because you can't pass a cursor through COM, then on the client convert it to a cursor and bind it to a grid.
>
>Unless you are building a distributed application it makes no sense to move to three tiers. Just do a traditional 2-tiered client server with VFP and SQL server.
>
>Charlie