KeithTrangmar
Programmer
I've built a simple function into my DBC which interrogates a set of records from it's child tables and returns a character string. I've tested this locally within VFP and it all works tickety-boo.
My colleague, who works in VB.NET, now needs to be able to call this stored procedure using OLE/ODBC/whatever so that he can use the resulting string in his VB program.
He's managed to establish a connection to the DBC, and can actually browse my tables, but we don't want him to have to read them directly because we're working on separate applications, and his shouldn't have to be aware of my table structures in order to retrieve this information. It's only small, so we're keeping the functionality which understands each application's underlying database local to the application itself, and using the stored procedure as a "public" interface to it.
Has anyone actually done this, and if so can you please offer an example of how the call to the stored procedure should be phrased in order to retrieve it's results?
Thanks,
Keith Trangmar
Harlend Computer Services
Maidstone, Kent. UK.
My colleague, who works in VB.NET, now needs to be able to call this stored procedure using OLE/ODBC/whatever so that he can use the resulting string in his VB program.
He's managed to establish a connection to the DBC, and can actually browse my tables, but we don't want him to have to read them directly because we're working on separate applications, and his shouldn't have to be aware of my table structures in order to retrieve this information. It's only small, so we're keeping the functionality which understands each application's underlying database local to the application itself, and using the stored procedure as a "public" interface to it.
Has anyone actually done this, and if so can you please offer an example of how the call to the stored procedure should be phrased in order to retrieve it's results?
Thanks,
Keith Trangmar
Harlend Computer Services
Maidstone, Kent. UK.