Re: VB,ODBC & Stored Procedures
Date: 1995/07/28
Message-ID: <3vb5sc$t81_at_elaine21.Stanford.EDU>#1/1
In article <3vaaok$ikb_at_pheidippides.axion.bt.co.uk>,
Ronan Miles <milesr_at_bhnov1.agw.bt.co.uk> wrote:
>The correct SQL would be "BEGIN Create_Jane_doe;END".
>
>However, all this does is execute the procedure, ODBC does not have the
>ability (as far as I have ever found) to read any returned results from
>the procedure (or function).
>
The limitation of not being able to return result-sets, or handling input/output parameters is not an ODBC limitation (ODBC has a well defined interface for that and some drivers even have implemented it), but merely the result of not exploiting this feature at the Visual Basic side.....
VB is cool for fast MS-Windows applications developement, but if your application needs to do database access that goes further than displaying the result of "select * from employee" in a form, you should consider other tools.... (i.e. tools that give access to all sorts of functionality found in databases like master-detail relations, stored-procedures and that automatically take care of creating the layout for a form based on the description of a table, etc).
Edwin Meijer. Received on Fri Jul 28 1995 - 00:00:00 CEST