FormParent load opens FormChildA.
FormChildA btn click opens FormChildB.
(FormChildA and FormChildB are both children of FormParent)
(FormChildA and FormChildB are different forms)
Problem: FormChildA btn click can only open one instance for FormChildB. I
need multiple instances of FormChildB.
Any suggestions or ideas please.
tx,
Paul
26  1916 
your newFormB would then not be a child. It needs to be child of FormParent.
The original FormChildB and FormChildA are both declared in FormParent.
FormChildB is module level Public Shared
"Rob Teixeira [MVP]" <RobTeixeira@@msn.com> wrote in message
news:Ot***************@tk2msftngp13.phx.gbl... in FormChildA button click:
Dim newFormB as New FormChildB
newFormB.Show
-Rob Teixeira [MVP]
"Paul Mars" <pa************@netzero.com> wrote in message
news:OF**************@tk2msftngp13.phx.gbl... FormParent load opens FormChildA.
FormChildA btn click opens FormChildB.
(FormChildA and FormChildB are both children of FormParent)
(FormChildA and FormChildB are different forms)
Problem: FormChildA btn click can only open one instance for FormChildB.
I need multiple instances of FormChildB.
Any suggestions or ideas please.
tx,
Paul
in FormChildA button click:
Dim newFormB as New FormChildB
newFormB.Show
-Rob Teixeira [MVP]
"Paul Mars" <pa************@netzero.com> wrote in message
news:OF**************@tk2msftngp13.phx.gbl... FormParent load opens FormChildA.
FormChildA btn click opens FormChildB.
(FormChildA and FormChildB are both children of FormParent)
(FormChildA and FormChildB are different forms)
Problem: FormChildA btn click can only open one instance for FormChildB. I
need multiple instances of FormChildB.
Any suggestions or ideas please.
tx,
Paul
your newFormB would then not be a child. It needs to be child of FormParent.
The original FormChildB and FormChildA are both declared in FormParent.
FormChildB is module level Public Shared
"Rob Teixeira [MVP]" <RobTeixeira@@msn.com> wrote in message
news:Ot***************@tk2msftngp13.phx.gbl... in FormChildA button click:
Dim newFormB as New FormChildB
newFormB.Show
-Rob Teixeira [MVP]
"Paul Mars" <pa************@netzero.com> wrote in message
news:OF**************@tk2msftngp13.phx.gbl... FormParent load opens FormChildA.
FormChildA btn click opens FormChildB.
(FormChildA and FormChildB are both children of FormParent)
(FormChildA and FormChildB are different forms)
Problem: FormChildA btn click can only open one instance for FormChildB.
I need multiple instances of FormChildB.
Any suggestions or ideas please.
tx,
Paul
Dim newFormB as New FormChildB
newFormB.MDIParent = FormParent
newFormB.Show
-Rob Teixeira [MVP]
"Paul Mars" <pa************@netzero.com> wrote in message
news:O3******************@tk2msftngp13.phx.gbl... your newFormB would then not be a child. It needs to be child of
FormParent.
The original FormChildB and FormChildA are both declared in FormParent.
FormChildB is module level Public Shared
Dim newFormB as New FormChildB
newFormB.MDIParent = FormParent
newFormB.Show
-Rob Teixeira [MVP]
"Paul Mars" <pa************@netzero.com> wrote in message
news:O3******************@tk2msftngp13.phx.gbl... your newFormB would then not be a child. It needs to be child of
FormParent.
The original FormChildB and FormChildA are both declared in FormParent.
FormChildB is module level Public Shared
This will not work Rob. If I put this in ChildB, it would not recognize
"FormParent". Also, generally why make a second dim for multiple instances?
My code:
Public Class FormParent
Inherits System.Windows.Forms.Form
Windows Form Designer generated code
Public Shared childBInst As New childB
Private Sub OpenChildA_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles OpenChildA.Click
Dim childAInst As New childA
With childAInst
..MdiParent = Me
..Show()
..Text = "1st"
End With
childBInst.MdiParent = Me
End Sub
End Class
-------------------------------------
Public Class childA
Inherits System.Windows.Forms.Form
Windows Form Designer generated code
Private Sub OpenChildB_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles OpenChildB.Click
with FormParent.childBInst
..Show()
..Text = "2nd"
End With
End Sub
End Class
"Rob Teixeira [MVP]" <RobTeixeira@@msn.com> wrote in message
news:ON**************@tk2msftngp13.phx.gbl... Dim newFormB as New FormChildB
newFormB.MDIParent = FormParent
newFormB.Show
-Rob Teixeira [MVP]
"Paul Mars" <pa************@netzero.com> wrote in message
news:O3******************@tk2msftngp13.phx.gbl... your newFormB would then not be a child. It needs to be child of
FormParent.
The original FormChildB and FormChildA are both declared in FormParent.
FormChildB is module level Public Shared
This will not work Rob. If I put this in ChildB, it would not recognize
"FormParent". Also, generally why make a second dim for multiple instances?
My code:
Public Class FormParent
Inherits System.Windows.Forms.Form
Windows Form Designer generated code
Public Shared childBInst As New childB
Private Sub OpenChildA_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles OpenChildA.Click
Dim childAInst As New childA
With childAInst
..MdiParent = Me
..Show()
..Text = "1st"
End With
childBInst.MdiParent = Me
End Sub
End Class
-------------------------------------
Public Class childA
Inherits System.Windows.Forms.Form
Windows Form Designer generated code
Private Sub OpenChildB_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles OpenChildB.Click
with FormParent.childBInst
..Show()
..Text = "2nd"
End With
End Sub
End Class
"Rob Teixeira [MVP]" <RobTeixeira@@msn.com> wrote in message
news:ON**************@tk2msftngp13.phx.gbl... Dim newFormB as New FormChildB
newFormB.MDIParent = FormParent
newFormB.Show
-Rob Teixeira [MVP]
"Paul Mars" <pa************@netzero.com> wrote in message
news:O3******************@tk2msftngp13.phx.gbl... your newFormB would then not be a child. It needs to be child of
FormParent.
The original FormChildB and FormChildA are both declared in FormParent.
FormChildB is module level Public Shared
"Paul Mars" <pa************@netzero.com> schrieb This will not work Rob. If I put this in ChildB, it would not
recognize "FormParent". Also, generally why make a second dim for
multiple instances? My code:
Of course it doesn't recognize FormParent, but I think it's still the same
MDIParent, so you can also use the same MDIParent:
Dim newFormB as New FormChildB
newFormB.MDIParent = Me.MDIParent
newFormB.Show
--
Armin
How to quote and why: http://www.plig.net/nnq/nquote.html http://www.netmeister.org/news/learn2quote.html
"Paul Mars" <pa************@netzero.com> schrieb This will not work Rob. If I put this in ChildB, it would not
recognize "FormParent". Also, generally why make a second dim for
multiple instances? My code:
Of course it doesn't recognize FormParent, but I think it's still the same
MDIParent, so you can also use the same MDIParent:
Dim newFormB as New FormChildB
newFormB.MDIParent = Me.MDIParent
newFormB.Show
--
Armin
How to quote and why: http://www.plig.net/nnq/nquote.html http://www.netmeister.org/news/learn2quote.html
"Paul Mars" <pa************@netzero.com> wrote in message
news:u2**************@TK2MSFTNGP10.phx.gbl... This will not work Rob. If I put this in ChildB, it would not recognize
"FormParent".
Alright, I'll have to be a little more explicit. I should have typed this in
the first place :-)
The issue is that the MdiParent property needs a reference to the MDI form
class, not the name of the MDI form class. But since formA is already an MDI
child, this is easy.
In the childA button click event handler, type:
Dim formB as New childB
formB.MdiParent = Me.MdiParent
formB.Show
Also, generally why make a second dim for multiple instances?
You don't need a second Dim, but your property is a Shared instance.
You could use:
FormParent.childBInst = New childB
With FormParent.childBInst
.MdiParent = Me.MdiParent
.Show
End With
But the Shared reference will only point to the newest childB instance
anyway.
-Rob Teixeira [MVP]
My code:
Public Class FormParent
Inherits System.Windows.Forms.Form
Windows Form Designer generated code
Public Shared childBInst As New childB
Private Sub OpenChildA_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles OpenChildA.Click
Dim childAInst As New childA
With childAInst
.MdiParent = Me
.Show()
.Text = "1st"
End With
childBInst.MdiParent = Me
End Sub
End Class
-------------------------------------
Public Class childA
Inherits System.Windows.Forms.Form
Windows Form Designer generated code
Private Sub OpenChildB_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles OpenChildB.Click
with FormParent.childBInst
.Show()
.Text = "2nd"
End With
End Sub
End Class
"Rob Teixeira [MVP]" <RobTeixeira@@msn.com> wrote in message
news:ON**************@tk2msftngp13.phx.gbl... Dim newFormB as New FormChildB
newFormB.MDIParent = FormParent
newFormB.Show
-Rob Teixeira [MVP]
"Paul Mars" <pa************@netzero.com> wrote in message
news:O3******************@tk2msftngp13.phx.gbl... your newFormB would then not be a child. It needs to be child of
FormParent.
The original FormChildB and FormChildA are both declared in
FormParent. FormChildB is module level Public Shared
"Paul Mars" <pa************@netzero.com> wrote in message
news:u2**************@TK2MSFTNGP10.phx.gbl... This will not work Rob. If I put this in ChildB, it would not recognize
"FormParent".
Alright, I'll have to be a little more explicit. I should have typed this in
the first place :-)
The issue is that the MdiParent property needs a reference to the MDI form
class, not the name of the MDI form class. But since formA is already an MDI
child, this is easy.
In the childA button click event handler, type:
Dim formB as New childB
formB.MdiParent = Me.MdiParent
formB.Show
Also, generally why make a second dim for multiple instances?
You don't need a second Dim, but your property is a Shared instance.
You could use:
FormParent.childBInst = New childB
With FormParent.childBInst
.MdiParent = Me.MdiParent
.Show
End With
But the Shared reference will only point to the newest childB instance
anyway.
-Rob Teixeira [MVP]
My code:
Public Class FormParent
Inherits System.Windows.Forms.Form
Windows Form Designer generated code
Public Shared childBInst As New childB
Private Sub OpenChildA_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles OpenChildA.Click
Dim childAInst As New childA
With childAInst
.MdiParent = Me
.Show()
.Text = "1st"
End With
childBInst.MdiParent = Me
End Sub
End Class
-------------------------------------
Public Class childA
Inherits System.Windows.Forms.Form
Windows Form Designer generated code
Private Sub OpenChildB_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles OpenChildB.Click
with FormParent.childBInst
.Show()
.Text = "2nd"
End With
End Sub
End Class
"Rob Teixeira [MVP]" <RobTeixeira@@msn.com> wrote in message
news:ON**************@tk2msftngp13.phx.gbl... Dim newFormB as New FormChildB
newFormB.MDIParent = FormParent
newFormB.Show
-Rob Teixeira [MVP]
"Paul Mars" <pa************@netzero.com> wrote in message
news:O3******************@tk2msftngp13.phx.gbl... your newFormB would then not be a child. It needs to be child of
FormParent.
The original FormChildB and FormChildA are both declared in
FormParent. FormChildB is module level Public Shared
Hi Paul,
In this thread is everytime a new instance of an form created in the
samples.
I showed you withouth doing that. The way I did it was create them shared in
the mdi container.
Keep in mind that what is showed in this thread is a totally different
approache from what I showed. (I showed it you only because you did ask to
make it able to open form3 in form2 by the way, wherein I showed you that
you can show and hide it everywhere)
When you do not take the approach I took, there is in my opinon also no need
to create the form shared in my opinion, however keep than in mind that the
information on the form will also everytime in default new state.
Cor
Hi Paul,
In this thread is everytime a new instance of an form created in the
samples.
I showed you withouth doing that. The way I did it was create them shared in
the mdi container.
Keep in mind that what is showed in this thread is a totally different
approache from what I showed. (I showed it you only because you did ask to
make it able to open form3 in form2 by the way, wherein I showed you that
you can show and hide it everywhere)
When you do not take the approach I took, there is in my opinon also no need
to create the form shared in my opinion, however keep than in mind that the
information on the form will also everytime in default new state.
Cor
I tried and it does not work. Want see see my 200k app?
p
"Armin Zingler" <az*******@freenet.de> wrote in message
news:40***********************@news.freenet.de... "Paul Mars" <pa************@netzero.com> schrieb This will not work Rob. If I put this in ChildB, it would not
recognize "FormParent". Also, generally why make a second dim for
multiple instances? My code:
Of course it doesn't recognize FormParent, but I think it's still the same
MDIParent, so you can also use the same MDIParent:
Dim newFormB as New FormChildB
newFormB.MDIParent = Me.MDIParent
newFormB.Show
--
Armin
How to quote and why:
http://www.plig.net/nnq/nquote.html
http://www.netmeister.org/news/learn2quote.html
I tried and it does not work. Want see see my 200k app?
p
"Armin Zingler" <az*******@freenet.de> wrote in message
news:40***********************@news.freenet.de... "Paul Mars" <pa************@netzero.com> schrieb This will not work Rob. If I put this in ChildB, it would not
recognize "FormParent". Also, generally why make a second dim for
multiple instances? My code:
Of course it doesn't recognize FormParent, but I think it's still the same
MDIParent, so you can also use the same MDIParent:
Dim newFormB as New FormChildB
newFormB.MDIParent = Me.MDIParent
newFormB.Show
--
Armin
How to quote and why:
http://www.plig.net/nnq/nquote.html
http://www.netmeister.org/news/learn2quote.html
I tried your method before and it did not work for me. May be my fault, I
will try it again.
I will also try Rob's last post.
Except right now my wife said "Beach Time". It is nice out. Thanks for all
your help so far, see ya later this afternoon(hopefully).
Paul
"Cor Ligthert" <no**********@planet.nl> wrote in message
news:ud**************@TK2MSFTNGP09.phx.gbl... Hi Paul,
In this thread is everytime a new instance of an form created in the
samples.
I showed you withouth doing that. The way I did it was create them shared
in the mdi container.
Keep in mind that what is showed in this thread is a totally different
approache from what I showed. (I showed it you only because you did ask to
make it able to open form3 in form2 by the way, wherein I showed you that
you can show and hide it everywhere)
When you do not take the approach I took, there is in my opinon also no
need to create the form shared in my opinion, however keep than in mind that
the information on the form will also everytime in default new state.
Cor
I tried your method before and it did not work for me. May be my fault, I
will try it again.
I will also try Rob's last post.
Except right now my wife said "Beach Time". It is nice out. Thanks for all
your help so far, see ya later this afternoon(hopefully).
Paul
"Cor Ligthert" <no**********@planet.nl> wrote in message
news:ud**************@TK2MSFTNGP09.phx.gbl... Hi Paul,
In this thread is everytime a new instance of an form created in the
samples.
I showed you withouth doing that. The way I did it was create them shared
in the mdi container.
Keep in mind that what is showed in this thread is a totally different
approache from what I showed. (I showed it you only because you did ask to
make it able to open form3 in form2 by the way, wherein I showed you that
you can show and hide it everywhere)
When you do not take the approach I took, there is in my opinon also no
need to create the form shared in my opinion, however keep than in mind that
the information on the form will also everytime in default new state.
Cor
Got it, thanks. Much better then my Public Shared.
Paul
"Rob Teixeira [MVP]" <RobTeixeira@@msn.com> wrote in message
news:Os**************@TK2MSFTNGP11.phx.gbl...
"Paul Mars" <pa************@netzero.com> wrote in message
news:u2**************@TK2MSFTNGP10.phx.gbl... This will not work Rob. If I put this in ChildB, it would not recognize
"FormParent".
Alright, I'll have to be a little more explicit. I should have typed this
in the first place :-)
The issue is that the MdiParent property needs a reference to the MDI form
class, not the name of the MDI form class. But since formA is already an
MDI child, this is easy.
In the childA button click event handler, type:
Dim formB as New childB
formB.MdiParent = Me.MdiParent
formB.Show
Also, generally why make a second dim for multiple instances?
You don't need a second Dim, but your property is a Shared instance.
You could use:
FormParent.childBInst = New childB
With FormParent.childBInst
.MdiParent = Me.MdiParent
.Show
End With
But the Shared reference will only point to the newest childB instance
anyway.
-Rob Teixeira [MVP]
My code:
Public Class FormParent
Inherits System.Windows.Forms.Form
Windows Form Designer generated code
Public Shared childBInst As New childB
Private Sub OpenChildA_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles OpenChildA.Click
Dim childAInst As New childA
With childAInst
.MdiParent = Me
.Show()
.Text = "1st"
End With
childBInst.MdiParent = Me
End Sub
End Class
-------------------------------------
Public Class childA
Inherits System.Windows.Forms.Form
Windows Form Designer generated code
Private Sub OpenChildB_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles OpenChildB.Click
with FormParent.childBInst
.Show()
.Text = "2nd"
End With
End Sub
End Class
"Rob Teixeira [MVP]" <RobTeixeira@@msn.com> wrote in message
news:ON**************@tk2msftngp13.phx.gbl... Dim newFormB as New FormChildB
newFormB.MDIParent = FormParent
newFormB.Show
-Rob Teixeira [MVP]
"Paul Mars" <pa************@netzero.com> wrote in message
news:O3******************@tk2msftngp13.phx.gbl...
> your newFormB would then not be a child. It needs to be child of
FormParent.
>
> The original FormChildB and FormChildA are both declared in FormParent. > FormChildB is module level Public Shared
>
Got it, thanks. Much better then my Public Shared.
Paul
"Rob Teixeira [MVP]" <RobTeixeira@@msn.com> wrote in message
news:Os**************@TK2MSFTNGP11.phx.gbl...
"Paul Mars" <pa************@netzero.com> wrote in message
news:u2**************@TK2MSFTNGP10.phx.gbl... This will not work Rob. If I put this in ChildB, it would not recognize
"FormParent".
Alright, I'll have to be a little more explicit. I should have typed this
in the first place :-)
The issue is that the MdiParent property needs a reference to the MDI form
class, not the name of the MDI form class. But since formA is already an
MDI child, this is easy.
In the childA button click event handler, type:
Dim formB as New childB
formB.MdiParent = Me.MdiParent
formB.Show
Also, generally why make a second dim for multiple instances?
You don't need a second Dim, but your property is a Shared instance.
You could use:
FormParent.childBInst = New childB
With FormParent.childBInst
.MdiParent = Me.MdiParent
.Show
End With
But the Shared reference will only point to the newest childB instance
anyway.
-Rob Teixeira [MVP]
My code:
Public Class FormParent
Inherits System.Windows.Forms.Form
Windows Form Designer generated code
Public Shared childBInst As New childB
Private Sub OpenChildA_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles OpenChildA.Click
Dim childAInst As New childA
With childAInst
.MdiParent = Me
.Show()
.Text = "1st"
End With
childBInst.MdiParent = Me
End Sub
End Class
-------------------------------------
Public Class childA
Inherits System.Windows.Forms.Form
Windows Form Designer generated code
Private Sub OpenChildB_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles OpenChildB.Click
with FormParent.childBInst
.Show()
.Text = "2nd"
End With
End Sub
End Class
"Rob Teixeira [MVP]" <RobTeixeira@@msn.com> wrote in message
news:ON**************@tk2msftngp13.phx.gbl... Dim newFormB as New FormChildB
newFormB.MDIParent = FormParent
newFormB.Show
-Rob Teixeira [MVP]
"Paul Mars" <pa************@netzero.com> wrote in message
news:O3******************@tk2msftngp13.phx.gbl...
> your newFormB would then not be a child. It needs to be child of
FormParent.
>
> The original FormChildB and FormChildA are both declared in FormParent. > FormChildB is module level Public Shared
>
never mind, but thanks! I got it now, see below.
"Armin Zingler" <az*******@freenet.de> wrote in message
news:40***********************@news.freenet.de... "Paul Mars" <pa************@netzero.com> schrieb I tried and it does not work. Want see see my 200k app?
Yes. My email address is valid (use the whole address).
--
Armin
How to quote and why:
http://www.plig.net/nnq/nquote.html
http://www.netmeister.org/news/learn2quote.html
never mind, but thanks! I got it now, see below.
"Armin Zingler" <az*******@freenet.de> wrote in message
news:40***********************@news.freenet.de... "Paul Mars" <pa************@netzero.com> schrieb I tried and it does not work. Want see see my 200k app?
Yes. My email address is valid (use the whole address).
--
Armin
How to quote and why:
http://www.plig.net/nnq/nquote.html
http://www.netmeister.org/news/learn2quote.html
Hi Paul, Got it, thanks. Much better then my Public Shared.
This is the same as what Herfried and I showed you in the other thread,
however you said that did not fit you.
Strange!
Cor
Hi Paul, Got it, thanks. Much better then my Public Shared.
This is the same as what Herfried and I showed you in the other thread,
however you said that did not fit you.
Strange!
Cor
I did not understand it. So the way I tried it, did not work. Me is a
beginner.
P
"Cor Ligthert" <no**********@planet.nl> wrote in message
news:uN**************@tk2msftngp13.phx.gbl... Hi Paul,
Got it, thanks. Much better then my Public Shared.
This is the same as what Herfried and I showed you in the other thread,
however you said that did not fit you.
Strange!
Cor
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics | |
by: Maarten |
last post by:
Hi all,
I' facing a problem here that i am stucked with since i started with.net
in vb6.0 i used for example Form1.txtName.text = "test"
in vb.net i used ...
|
by: Paul Mars |
last post by:
FormParent load opens FormChildA.
FormChildA btn click opens FormChildB.
(FormChildA and FormChildB are both children of FormParent)
(FormChildA and FormChildB are different forms)
Problem:...
|
by: Siv |
last post by:
Hi,
I have an MDI application that uses a generic "ShowPage" routine in a module that is called when I want to display a child form. The basic idea is that in the module I have declared each form...
|
by: Prabhudhas Peter |
last post by:
If I click a menu to open a form which already open...the vb.net opens a new
window while existing open window is there...i want to restric the opening of
a new instance of an already opened...
|
by: Quina |
last post by:
Hi. Is there someone that can tell me how can I have multiple screens
on the the same form, displaying only on at the time?
Thank you all for any replys.
Joćo Carias
| | |
by: Stampede |
last post by:
Hello,
I created a Windows Application Project and tried to create a MDI-based
application. So I created a new MDI-parent with the creation wizzard. Then I
created a default form and tried to make...
|
by: mabond |
last post by:
Hi
Can't get my head round something which I reckon should be simple.
My app has a main form (frmMain). MdiContainer set to true.
A menu item triggers a new form (frmSelect) whose parent is...
|
by: Kevin |
last post by:
I've got an mdiParent form. I open an instance of a child form like
this:
Dim frmChild as New frmCustomers
frmChild.Show()
I've got a few of these open at a time. On each frmChild I open...
|
by: marktang |
last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However,...
|
by: Hystou |
last post by:
Overview:
Windows 11 and 10 have less user interface control over operating system update behaviour than previous versions of Windows. In Windows 11 and 10, there is no way to turn off the Windows...
|
by: tracyyun |
last post by:
Dear forum friends,
With the development of smart home technology, a variety of wireless communication protocols have appeared on the market, such as Zigbee, Z-Wave, Wi-Fi, Bluetooth, etc. Each...
| | |
by: agi2029 |
last post by:
Let's talk about the concept of autonomous AI software engineers and no-code agents. These AIs are designed to manage the entire lifecycle of a software development projectplanning, coding, testing,...
|
by: isladogs |
last post by:
The next Access Europe User Group meeting will be on Wednesday 1 May 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM).
In this session, we are pleased to welcome a new...
|
by: conductexam |
last post by:
I have .net C# application in which I am extracting data from word file and save it in database particularly. To store word all data as it is I am converting the whole word file firstly in HTML and...
|
by: TSSRALBI |
last post by:
Hello
I'm a network technician in training and I need your help.
I am currently learning how to create and manage the different types of VPNs and I have a question about LAN-to-LAN VPNs.
The...
|
by: adsilva |
last post by:
A Windows Forms form does not have the event Unload, like VB6. What one acts like?
|
by: muto222 |
last post by:
How can i add a mobile payment intergratation into php mysql website.
| |
