This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(112.00000000000001, 21%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGR%3C/text%3E%3C/svg%3E)
Below is a snapshot of VBA logic; however, when attempting to port to a VB.NET app, I get compile errors on the ADODB data types (any datatype with prefix of "ad"; e.g., adInteger, etc.)
The web-site below contains the various data types for ADO. Are these data types not valid for VB.NET? Thanks in advance for any help you can provide.
https://www.w3schools.com/asp/ado_datatypes.asp
cmd = New ADODB.Command
With cmd
.ActiveConnection = conn
.CommandType = adCmdStoredProc
.CommandText = storedProcName
.NamedParameters = True
End With
param1 = cmd.CreateParameter("ReturnValue", adInteger, adParamReturnValue)
cmd.Parameters.Append(param1)
An object-oriented programming language developed by Microsoft that can be used in .NET.
Answer accepted by question author
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(153.6, 89%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJL%3C/text%3E%3C/svg%3E)
Hi @Giacomo Raucci ,
The data type of ADO can be used in vb.net, try DataTypeEnum.adInteger.
Best Regards.
Jiachen Li
If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Your answer was very close, I had to further qualify it with the prefix of ADODB; thus, ADODB.DataTypeEnum.adInteger. I also needed to qualify the command; thus, ADODB.CommandTypeEnum.adCmdStoredProc. Do I need a "Using" statement that eliminates the additional qualifying prefix?
Also, I have adParmreturnValue - how would this be qualified? Thanks again for all your help. I appreciate in advance if you know the answer to my other questions. Thanks, Giacomo
Your answer helped a lot. I had to fully qualify with ADODB.DataTypeEnum.adInteger. In addition, I had to fully qualify the command as well. I've got 2 follow-up questions (if you don't mind). Q1. I don't know what the prefix would be for AdParamReturnValue? Q2. Would a "Using" statement be helpful in eliminating the qualifying prefix? Thanks again for all your help. regards, Giacomo
Hi @Giacomo Raucci ,
Imports ADODB to omit the ADODB. part of the data type.
Thanks. That worked. I now have only 1 more compile error, requires a separate posting. Again, thank you, you've been very helpful.