VisualBasic-ODBC-Oracle, Limitations?!!
Date: Wed, 25 May 94 23:04:53 GMT
Message-ID: <769907093snx_at_hkchan.pc.my>
In article <1994May19.183143.5789_at_verifone> sanjay_p1_at_verifone.com writes:
> I am working on this setup since past couple of months, and found
I'm interested in this. What kinds of features are not available to VB
but possible in Oracle? I'm more experienced in VB but less
knowledgeable in Oracle.
> Very simple function call but effective in Visual Basic ie.e
I have recently tested out VB 3.0 Professional against Oracle 7 running
on Netware. I've encountered some of the problems you mentioned. For
starter, using dynaset to perform insert, update, delete is slow. It is
much faster to use ExecuteSQL( "insert into atable ..." ) etc but the
> a lot of limitations. There are a lot of good features provided by Oracle,
> but over my set up VisualBasic-ODBC-Oracle these features are of no use.
> ExecuteSQL just does not work! I dont know if I could execute the
> stored procedure from VB. Also when I have to Insert-Update-Delete
> records, I create Dynasets. And they take noticably long time.
> This case is just with few records arround 20 in the table, I wonder
> whats going to be the case when my number of records grow to say 10000!
>
> Has anybody faced this kind of situation? If so lets share it.