|
This should have been thought before even starting with the development.
What kind of application is it? Is it using anything new that was introduced in .Net 3.5? If not, just set the target framework to 2.0 and see if application works fine.
|
|
|
|
|
i just used webbrowser, System.Data.OleDb and Npgsql... where can i change this target? thanks
|
|
|
|
|
look for "project properties", there are a couple of ways to get there.
|
|
|
|
|
Well, i tried, but no sucess, it is asking for .net framework 3.5 to be installed
|
|
|
|
|
1. when you change the target setting, you have to rebuild.
2. when you also create an installer, you'd have to modify that one too. Don't ask for details, I don't have them.
|
|
|
|
|
Ok, thank you anyway, i will try again here... hugs
|
|
|
|
|
As Luc told, change the target framework from the project properties. MSDN would help on how to do that.
Also, you can very well use new "compiler features" available with .Net 3.5. Your code will still run fine on a computer with .Net framework 2.0.
|
|
|
|
|
i need help on usb drive. when a user inserts a usb drive, auto run starts and diplays some of the options to select from. what i want is to add my applications exe to the list of auto run when usb drive is inserted in usb port, so that i can select my application and do some aftermath. please help. simply i want usb drive to run my application when i insert it into my computer.
|
|
|
|
|
Please do not cross-post (put the same question in more than one forum). Very very rude!
Henry Minute
Do not read medical books! You could die of a misprint. - Mark Twain
Girl: (staring) "Why do you need an icy cucumber?"
“I want to report a fraud. The government is lying to us all.”
Why do programmers often confuse Halloween and Christmas? - Because 31 Oct = 25 Dec.
Business Myths of the Geek #4 'What you think matters.'
|
|
|
|
|
you should pick one forum to ask your question.
|
|
|
|
|
This[^] should get you started.
|
|
|
|
|
Hi everybody,
Once again I need help. I made a COM exposed vb.net lib for an old VB6 app. Which was tested (prior and after COM exposure) using a simple stand-alone .net app with the expected results. Then, used regasm ... to re-generate and register the .tlb file and tested it again using the VB6 app; so far so good.
Copied and registed the new dll and the .tlb files (did registed the .tlb) into two other machines; it all worked as expected. So I said to myself "I am ready to deploy", yeah right!
After following the exact same procedure with tha exact same files in the target machines, all I get is this message: "automation error" (quite explicit, right?)
To rule any missing .net dependencies out, I tested the stand-alone .net app in those machines, and everything works as expected, but can't make the VB6 app work. I ran out of ideas, and of course, bosses want my head!
Can anybody offer any ideas to save my skiny neck? Thank you all so much for your time and interest.
Best regards,
Alex.
|
|
|
|
|
Maybe the vb6 dll does not get registered during the installation.
My signature "sucks" today
|
|
|
|
|
Hi Abhinav,
Thank you for your responce. That was my first thought, no wait, it was not it, my first thought was "what the f..... @!$%%&^*@#$% is going on!" as you very well imagine
I did think of that, so I manually registered the .tlb without positive results.
I can't explain why it works only on some computers. They all (the good ones and the bad ones) have the same .net framework installed, SP, patches, etc. I think it has to do with a VB6 o another COM dll I have not been able to pin-point.
I even used a couple of tools to detect any missing dependecies, both COM and .net, but had no good luck.
|
|
|
|
|
alexvw wrote: Then, used regasm
You'd additionally need to run "regsvr32" for any OLE-controls (ActiveX components and the likes).
Additionally, you might want to check what version of MDAC is installed.
I are Troll 
|
|
|
|
|
Good day Eddy,
Thank you for your suggestion, I shall look into it! and will let you know the result.
Best regards.
|
|
|
|
|
What's the VB6 counterpart of the following codes?
To insert a record in database with command object parameters:
dim strSql as string
strSql = "Insert Into tblEmployees (EmpName,DeptartmentID,JoinDate) Values ('" & _
txtName.Text & "'," & Val(cboDepartment.Value) & ",@JoinDate)"
com = CreateCommand(strSql)
com.Parameters.Add(New SqlParameter("@JoinDate", SqlDbType.DateTime))
If (dtpJoinDate.Checked) Then
com.Parameters("@JoinDate").Value = Convert.ToDateTime(dtpJoinDate.Value)
Else
com.Parameters("@JoinDate").Value = DBNull.Value
End If
If com.ExecuteNonQuery = 1 Then
MsgBox("Record saved.")
End If
To obtain a record from database:
Dim drd As SqlDataReader
strSql = "Select EmpName,DeptID,JoinDate From tblEmployees Where EmpID=1001"
drd = CreateReader(strSql)
If drd.Read Then
txtName.Text = drd("EmpName")
cboDepartment.Value = drd("DepartmentID")
If IsDBNull(drd("JoinDate")) Then
dtpJoinDate.ResetText()
dtpJoinDate.Checked = False
Else
dtpJoinDate.Value = drd("JoinDate")
End If
End If
drd.Close()
|
|
|
|
|
See here.
My signature "sucks" today
|
|
|
|
|
You need to include references to SQL in VB6. But I doubt if it is supported..
|
|
|
|
|
It's supported
|
|
|
|
|
Hi,
You can find an example on VB6 and ADO over here[^].
I are Troll
|
|
|
|
|
Sorry for not to be specific. I want to get the vb6 counterpart for passing dbnull value to database and getting the datareader object (recordset object in case of vb6) and check for dbnull value of one or all of its fields. The following blocks to be specific:
com.Parameters.Add(New SqlParameter("@JoinDate", SqlDbType.DateTime))
If (dtpJoinDate.Checked) Then
com.Parameters("@JoinDate").Value = Convert.ToDateTime(dtpJoinDate.Value)
Else
com.Parameters("@JoinDate").Value = DBNull.Value
End If
If IsDBNull(drd("JoinDate")) Then
'statements.......
'....................
Else
'statements.......
'....................
End If
I want the vb6 counterpart of the upper mentioned blocks (specially the bolded lines) in terms of recordset objects. I'm acquainted in handling recordset objects. Hope this time I'm more specific.
|
|
|
|
|
That would be something along these lines;
Dim MyParam As ADODB.Parameter
If ... Then
Set MyParam = MyCom.CreateParameter("JoinDate", adDate, adParamInput, dtpMyCalendar.value)
Else
Set MyParam = MyCom.CreateParameter("JoinDate", adDate, adParamInput, Noting)
End If
MyCom.Parameters.Append MyPara
Set MyRecordSet = MyCom.Execute
If IsNull(MyRecordSet(k).Value) Then
I are Troll
|
|
|
|
|
Private con As ADODB.Connection
Private Sub cmdOk_Click()
Dim com As ADODB.Command
Dim lngRetVal As Long
On Error GoTo ErrorHandler
'If Not Validate Then Exit Sub
If strItemID = Empty Then
strSql = "Insert Into tblItemList (ItemID,Item,CategoryID,Quantity,Rate,Half,HalfQuantity,HalfRate,ExpiryDate) Values ('" & _
ReplaceQuote(txtItemID.Text) & "','" & ReplaceQuote(txtItem.Text) & "'," & SetDataCombo(cboCategory) & ",'" & _
ReplaceQuote(txtQuantity.Text) & "'," & Val(txtRate.Text) & "," & IIf(chkHalfAvailable.Value, 1, 0) & ",'" & _
ReplaceQuote(txtHalfQuantity.Text) & "'," & Val(txtHalfRate.Text) & ",?)"
Else
strSql = "Update tblItemList Set ItemID='" & ReplaceQuote(txtItemID.Text) & "',Item='" & ReplaceQuote(txtItem.Text) & "'," & _
"CategoryID=" & SetDataCombo(cboCategory) & ",Quantity='" & ReplaceQuote(txtQuantity.Text) & "',Rate=" & _
Val(txtRate.Text) & ",Half=" & IIf(chkHalfAvailable.Value, 1, 0) & ",HalfQuantity='" & ReplaceQuote(txtHalfQuantity.Text) & "'," & _
"HalfRate=" & Val(txtHalfRate.Text) & ",ExpiryDate=?" & " Where ItemID='" & strItemID & "'"
End If
Set com = CreateCommand(strSql)
com.Parameters.Append com.CreateParameter("ExpiryDate", adDate, adParamInput)
If Not IsNull(dtpExpiry.Value) Then
com("ExpiryDate") = CDate(dtpExpiry.Value)
Else
'Using Nothing instead of Null in the following line generates an error- ‘Application uses a value of the wrong type for the current operation’.
com("ExpiryDate") = Null
End If
com.Execute lngRetVal, adCmdText, adExecuteNoRecords
If lngRetVal = 1 Then
Msgbox "Record saved."
Unload Me
End If
CloseConnection
strSql = Empty
Exit Sub
ErrorHandler:
CloseConnection
strSql = Empty
MsgBox "The following error has occurred:" & vbCrLf & Err.Description, vbCritical, "Error"
End Sub
Private Sub OpenConnection()
If con Is Nothing Then
Set con = New ADODB.Connection
con.Open "Provider=SQLOLEDB.1;Data Source=MyServer;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=TestDB"
End If
End Sub
Private Sub CloseConnection()
If Not con Is Nothing And con.State = adStateOpen Then
con.Close
Set con = Nothing
End If
End Sub
Private Function CreateCommand(strQuery As String) As ADODB.Command
Dim com As New ADODB.Command
OpenConnection
com.ActiveConnection = con
com.CommandText = strQuery
Set CreateCommand = com
End Function
Now about the problem. When I try to save, the system throws an error- 'The conversion from datetime data type to smalldatetime data type resulted in a smalldatetime overflow error'.
When I change the database table column data type to datetime and try to save the data from the form, it saves the default datetime value i.e. 31/12/1899 12:00:00 AM irrespective of what I pass through the parameter. Please help me sort out this problem, preferrably with the smalldatetime data type instead of the datetime as my application mainly deals with it. 
|
|
|
|
|
Hi,
Good work, seems you're almost there
What type of database are you using? You might be able to pass a DateTime and to convert that to a SmallDateTime in the SQL-statement itself. That would look something like this for the update-part of the statement;
"HalfRate=" & Val(txtHalfRate.Text) &
",ExpiryDate=convert(smalldatetime,?) " &
" Where ItemID='" & strItemID & "'"
Alternative, you could pass a DateTime to a stored procedure and to convert it to a SmallDateTime within that stored procedure. As a last resort you could pass them as a constant datetime-value, formatting the string by hand. That would resemble this;
"HalfRate=" & Val(txtHalfRate.Text) &
",ExpiryDate=#" & Format(CDate(dtpExpiry.Value), "mm/dd/yy") & "# " &
" Where ItemID='" & strItemID & "'"
You're already using strings to add the other values into the command-object; those would best be parameter-objects (also using CreateParameter), even though that adds to the amount of work. It will make the code easier to maintain in the future.
I are Troll
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
