Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
ADO recordsets & Oracle
Message
De
14/12/2001 10:16:43
 
 
À
14/12/2001 03:23:06
Information générale
Forum:
Visual FoxPro
Catégorie:
Base de données, Tables, Vues, Index et syntaxe SQL
Divers
Thread ID:
00593217
Message ID:
00594396
Vues:
37
>>loCM.CommandText = "GetExpenseCursor"
>
>Hi there,
>
>Tried it and got more of the same. A friend of mine has warned me that using VB or VFP with Oracle can be a very painful experience. I'm afraid my boss has taken us down the wrong route...we should either be using SQL server or Java...told him so.
>
>Thanks for your input. To be quite honest I think we're barking up the wrong tree big time here. My boss wants to use a private network using TCP/IP and I think we should head down the internet route. The stuff that's available from West wind looks like it should do the trick. I'm not sure what the 'pain' level is like, but there's only one way to find out.
>
>Anwyay, I think I'm gonna drop this for the moment.
>
>Thanks for the help.
>
>Pablo

What if you add the stuff I took out? (the fully qualified db name for the sp)

FWIW, you can obtain the stored procedure names with ADOX. If even after using the name that is returned by the Oracle provider it doesn't work then I have not much to add. See sample below: (untested)
oCatalog = CreateObject("ADOX.Catalog")
oCatalog.ActiveConnection = oCn
For Each oProc In oCatalog.Procedures
  ? oProc.Name
Next
Where oCn is an open ADO connection object to the appropriate DB using the Oracle OLEDB provider. (and assuming you have permissions to enumerate the database objects)
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform