|
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
|
|
|
|
|
|
|
I'm looking to create a COM component to run on my Web App. The Web App is server ASP pages and needs to access a COM component for retrieving items from a database. The reason I'm considering COM is because I would like to use DB Connection Pooling to interact with SQL server. I know there is a way to register a .net assembly as a COM component. My question is, I would like to know if I will be able to access the COM using VBScript.
For example, can I use something like
Set PageRenderer = Server.CreateObject("MyCompany.PageRenderer")
and then call methods on it?
Thanks for any input!
|
|
|
|
|
So long as the target machine has the appropriate version of the .NET Framework installed, this will work. Once the component is registered, it works just like any other COM component.
RageInTheMachine9532
"...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
|
|
|
|
|
Hi, My database has two table:
1. tblMain<br />
2. tblChild
tblMain is the main table and tblChild is the child table which has relationship (one to many) from tblMain to tblChild.
In VB.Net I use COM ADO 2.0 to access my access database. In this project, one item in tblMain can have many item in tblChild . The problem that i face is I want to delete one item from tblChild , but it delete all item that relate to tblMain . Example: in tblMain I have the reocrd as befow.
SubjID (Primary key) SubjName
s001 Computer
s002 Mathematic
s003 Economic
and tblChild have the following field and data:
SubjID (Foreign Key) FilePath
s001 C:\VB.doc
s001 C:\Doc\VBdotNet.doc
s002 D:\Prog\Algo.txt
s003 C:\Eco\SoutEas.doc
s003 C:\Eco\Elect.txt
s003 C:\Eco\Oil.doc
And then I want to delete
s003 C:\Eco\Oil.doc
But I after I delete my tblChild table remain only:
SubjID (Foreign Key) FilePath
s001 C:\VB.doc
s001 C:\Doc\VBdotNet.doc
s002 D:\Prog\Algo.txt
The record:
s003 C:\Eco\SoutEas.doc
s003 C:\Eco\Elect.txt
Also delete too, I don't know why??? Can any one told me to solve this prblem...
A thousand mile of journey, begin with the first step.
APO-CEDC
Save Children Norway-Cambodia Office
|
|
|
|
|
Probably your sql statement isn´t right.
For this case, the sql statement should be:
DELETE * FROM tblChild WHERE FilePath='C:\Eco\Oil.doc'
|
|
|
|
|
Now I have an idea but did not try yet. I will do this:
DELETE * FROM tblChild WHERE tblChild.SubjID='s003' AND tblChild.FilePath='C:\Eco\Oil.doc'
A thousand mile of journey, begin with the first step.
APO-CEDC
Save Children Norway-Cambodia Office
|
|
|
|
|
That´s right. But if you let me give you an advice: You could put an PK field in tblChild and work with that field. I don´t know if this would make things easier but...
Good luck.
|
|
|
|
|
Thank you very much for your advice. May be I need to try with this way, I really worry because the deadline of my project is comming soon.
A thousand mile of journey, begin with the first step.
APO-CEDC
Save Children Norway-Cambodia Office
|
|
|
|