|
Infragistics[^] has a great grid control. Comes with the NetAdvantage package, but is not cheap.
RageInTheMachine9532
"...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
|
|
|
|
|
I'm having a difficult time figuring out how to set up a group of three RadioButton options.
Should I have three different bit fields in my database or one numeric field?
Also, what do you bind to? I thought that I should be binding Checked to my bit field in the database, like you can do for the CheckBox.
|
|
|
|
|
I have a Windows Application which calls / references a Class Library that I'm writing.
From within the Class Library code I want to find out the name of the application that is calling the class.
I tried System.Environment.Username which went too far back and gave me my network signon.
Any info will be appreciated... 
Lost in the vast sea of .NET
|
|
|
|
|
KreativeKai wrote:
I tried System.Environment.Username which went too far back and gave me my network signon.
 What did you expect with a property name of Username?
You could use the Process class in your library code and call Process.GetCurrentProcess to, obviously, get the current process and then return that objects ProcessName:
Imports System.Diagnostics
.
.
Dim name As String = Process.GetCurrentProcess().ProcessName
RageInTheMachine9532
"...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
|
|
|
|
|
That worked perfectly!! Thanks!! 
Lost in the vast sea of .NET
|
|
|
|
|
I am having a problem calling functions from a C based DLL with VB version 6.0.
I was given the DLL and do not have the original code, however I have found out that the function I am calling is external to the DLL, but has an unknown calling type. I believe the function must have a _stdcall (standard calling type) for a VB application to use it. Is there anyway I can fix this problem? Or does anyone have any ideas?
Thanks
|
|
|
|
|
What function are you calling? If it's outside the .DLL you were given, then that .DLL has no bearing on the problem what-so-ever. And your right, the function must follow the _stdcall calling convention in order to work with VB6. There is no way around this unless you wrap the call in a custom written (C++) .DLL that will pass parameters and returns back and forth between the function call and VB.
RageInTheMachine9532
"...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
|
|
|
|
|
I have that one problem figured out and I am now able to access the functions; however, I am having a new problem.
I am trying to open a TCPIP connection through a specific piece of software to which I have the DLL that allows me to make the connection.
The function is:
Private Declare Function QTM_OpenTCPIPConnection Lib "QTMClient.dll" _
(ByVal strDestination As String, ByVal strServiceName As String) _
As Boolean
I am trying to set a check to determine if the function was opened successfully. Something like:
errtcp = QTM_OpenTCPIPConnection txtRemoteIP.Text, val(txtRemotePort.Text)
if errtcp = true then
isOpen = True
else
MsgBox "error"
Exit Sub
end if
But no matter what I try errtcp is always FALSE!! Or VB wont let me write the IF statement. I know the connection is working properly because I have software written in C that allows me to open the TCPIP connection. I can't get it to work in VB.
Any advice would be greatly appreciated!!
|
|
|
|
|
I'm not familiar with the library at all, and frankly, it's not supported here at CP. Usually, if a function constantly returns a failure result, it's because your not passing the parameters correctly.
It's not a problem with VB. It can pass parameters to most functions without a problem, but only if the parameters are defined properly in the Declare statement.
RageInTheMachine9532
"...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
|
|
|
|
|
can i run .net applications in Windows 95
Yuvaraj N
|
|
|
|
|
As far as I know, .Net is not support with windows 95. It might be support from windows 98 to winxp.
A thousand mile of journey, begin with the first step.
APO-CEDC
Save Children Norway-Cambodia Office
|
|
|
|
|
No, you can't. The minimum is Windows 98, and even then, there's some stuff that's not supported. The REAL minimum should be Windows NT 4 SP 6a.
RageInTheMachine9532
"...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
|
|
|
|
|
Where can I find out what's not supported under Win98?
|
|
|
|
|
I haven't seen anyt site with any kind of a list of features not supported. But, ASP.NET will not work on 98. But, keep in mind that the .NET Framework Base Class Library (BCL) and components are largely wrappers for the Win32 API. There are functions in the API that are not available on anything lower than Windows NT.
RageInTheMachine9532
"...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
|
|
|
|
|
 Hi there, again i ask you a solution for my problem that
i want to add a new rows to the datagrid programmatically,rather than bind it to a Database
|
|
|
|
|
Hi,
In my project i have 4 forms the starting form is MDI Container.what i want to do is, to open a child form from another child form e.g. a search form opens another child form for the main MDI container. I have tried a lot of things but to no sucess. Help!
Thanks
Nitin
|
|
|
|
|
Can you post the code that you face the problem on this forum?
A thousand mile of journey, begin with the first step.
APO-CEDC
Save Children Norway-Cambodia Office
|
|
|
|
|
Dim ChildForm1 As frmChildForm = New frmChildform
Dim MDIForm as frmMDIForm = New frmMDIForm
ChildForm1.MdiParent = MDIForm
ChildForm1.Show()
The MDIForm is the main form and i am calling this code from another ChildForm but it's not working, instead it opens ChildForm1 as a new form with no MDIParent.Help!
Thanks.
|
|
|
|
|
The problem is that your creating a new instance of your MDIParent form and passing that to the child. Instead, pass the MdiParent of the current child form to the new child form. (In a proper MDI application, all child form creation should be left up to the MDIParent, not it's child forms!)
Dim ChildForm1 As frmChildForm = New frmChildform
ChildForm1.MdiParent = Me.MdiParent
ChildForm1.Show()
RageInTheMachine9532
"...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
|
|
|
|
|
Thanks Dave I have tried ur code but the problem is still the same it is not opening as a child window.
|
|
|
|
|
Like I said, it's better to have the child creation code in the Parent.
But, we'd have to see more of your code. There's something else you're doing/not doing that we can't see.
RageInTheMachine9532
"...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
|
|
|
|
|
Thanks Dave for working on my problem.
This is what i am writing in my MDI form after setting it IsMdiContainer property to true.
Dim ChildForm As frmFind = New ChildForm
ChildForm.MdiParent = Me
ChildForm.Show()
Rest U know what I am doing in child form.
Thanks a lot.
|
|
|
|
|
The not what I was looking for...
What else is happening in your child form code, around the place where the new form is created? I'm looking for things like, are you closing the child form that creates your second child form?
RageInTheMachine9532
"...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
|
|
|
|
|
Yes I'm closing the childform which creates a new child form but only alter creating and showing the new childform.
Dim ChildForm As frmFind = New ChildForm
ChildForm.MdiParent = Me
ChildForm.Show
Me.Close()
|
|
|
|
|
That's the problem! The old child form holds the reference that is keeping the new child form alive. Once the old child form is destroyed, any objects that it created are also destroyed! That's why I said leave the child form creation up to the parent and not another child!
RageInTheMachine9532
"...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
