Hi all, quick question - I need a bit of clarity.
If I have a public class with only Public Shared functions in it, in an APS.NET web app (for common procedures) is it
safe (since multiple web pages, can at any time access the code within)
The reason for a Shared class like this is that, it would contain all of the useful functions we put together over time
like FillList, SelectListItem, FindLastItemInList, EmptyList, SortList etc etc etc
Example below - a simple routine that fills a dropdownlist. Would it be safe being accessed at multiple times by
the APSX pages? Forget the fact the code might not be perfect - only that I would like to arrange my code this way.
I suspect there may be caveats - but I need a more knowledgeable opinion.
Public Class MyUtils
Public Shared Function FillList(ByVal objList As DropDownList, ByVal sSql As String, ByVal sConnection As String) As
Boolean
Dim dr As OleDb.OleDbDataReader, Li As ListItem
Dim cn As New OleDb.OleDbConnection(sConnection)
Dim cmd As OleDb.OleDbCommand
Try
cn.Open()
cmd = New OleDb.OleDbCommand(sSql, cn)
dr = cmd.ExecuteReader(CommandBehavior.CloseConnection)
While dr.Read
Li = New ListItem
Li.Text = dr(0)
Li.Value = dr(1)
objList.Items.Add(Li)
End While
Catch ex As Exception
Stop
Return False
Finally
cmd.Dispose()
If dr Is Nothing = False Then dr.Close()
cn.Close()
End Try
Return True
End Function
Public Function EmptyList(...)
...
End Function
...
...
'Other Public Shared Functions...
...
...
End Class
Usage...
FillList(cmbListOfNames, AppSettings("SQL.PEOPLE"),AppSettings("CONSTRING.M ANAGEMENT"))
16  1305 
Just a suggestion (everyone has their own ways of accomplishing things)...
But, one option would be to have that particular class inherit the standard
'Web.UI.Page' class. For example, your class could be called 'PageBase' and
look like the following:
public class PageBase : System.Web.UI.Page
{
......
}
Put all of your common routines (methods) and (properties) in this
particular class. Then, when you want to create a new webform simply
inherit this class instead of of the normal 'System.Web.UI.Page' class (the
default that gets setup for you with Visual Studio is to inherit from the
Web.UI.Page class, after it does that simply put in your own class). For
example:
public class DealerLinksList : myNameSpace.PageBase
{
....
}
You can make these methods 'protected' within your 'PageBase' class. Every
webform you create from that class will have access to these common methods
and procedures without instantiating different objects/etc. Again, you may
get 30 people responding and 30 different methods.. I like this particular
method because it provides me with an OO type capability (inheritence) and
changes can simply be made to the 'parent' class and only those members that
directly inherit from that parent class are affected...
"Stevie_mac" <no******@please.com> wrote in message
news:e1**************@TK2MSFTNGP10.phx.gbl... Hi all, quick question - I need a bit of clarity.
If I have a public class with only Public Shared functions in it, in an
APS.NET web app (for common procedures) is it safe (since multiple web pages, can at any time access the code within)
The reason for a Shared class like this is that, it would contain all of
the useful functions we put together over time like FillList, SelectListItem, FindLastItemInList, EmptyList, SortList etc
etc etc
Example below - a simple routine that fills a dropdownlist. Would it be
safe being accessed at multiple times by the APSX pages? Forget the fact the code might not be perfect - only that
I would like to arrange my code this way.
I suspect there may be caveats - but I need a more knowledgeable opinion.
Public Class MyUtils
Public Shared Function FillList(ByVal objList As DropDownList, ByVal
sSql As String, ByVal sConnection As String) As Boolean
Dim dr As OleDb.OleDbDataReader, Li As ListItem
Dim cn As New OleDb.OleDbConnection(sConnection)
Dim cmd As OleDb.OleDbCommand
Try
cn.Open()
cmd = New OleDb.OleDbCommand(sSql, cn)
dr = cmd.ExecuteReader(CommandBehavior.CloseConnection)
While dr.Read
Li = New ListItem
Li.Text = dr(0)
Li.Value = dr(1)
objList.Items.Add(Li)
End While
Catch ex As Exception
Stop
Return False
Finally
cmd.Dispose()
If dr Is Nothing = False Then dr.Close()
cn.Close()
End Try
Return True
End Function
Public Function EmptyList(...)
...
End Function
...
...
'Other Public Shared Functions...
...
...
End Class
Usage...
FillList(cmbListOfNames,
AppSettings("SQL.PEOPLE"),AppSettings("CONSTRING.M ANAGEMENT"))
Just a suggestion (everyone has their own ways of accomplishing things)...
But, one option would be to have that particular class inherit the standard
'Web.UI.Page' class. For example, your class could be called 'PageBase' and
look like the following:
public class PageBase : System.Web.UI.Page
{
......
}
Put all of your common routines (methods) and (properties) in this
particular class. Then, when you want to create a new webform simply
inherit this class instead of of the normal 'System.Web.UI.Page' class (the
default that gets setup for you with Visual Studio is to inherit from the
Web.UI.Page class, after it does that simply put in your own class). For
example:
public class DealerLinksList : myNameSpace.PageBase
{
....
}
You can make these methods 'protected' within your 'PageBase' class. Every
webform you create from that class will have access to these common methods
and procedures without instantiating different objects/etc. Again, you may
get 30 people responding and 30 different methods.. I like this particular
method because it provides me with an OO type capability (inheritence) and
changes can simply be made to the 'parent' class and only those members that
directly inherit from that parent class are affected...
"Stevie_mac" <no******@please.com> wrote in message
news:e1**************@TK2MSFTNGP10.phx.gbl... Hi all, quick question - I need a bit of clarity.
If I have a public class with only Public Shared functions in it, in an
APS.NET web app (for common procedures) is it safe (since multiple web pages, can at any time access the code within)
The reason for a Shared class like this is that, it would contain all of
the useful functions we put together over time like FillList, SelectListItem, FindLastItemInList, EmptyList, SortList etc
etc etc
Example below - a simple routine that fills a dropdownlist. Would it be
safe being accessed at multiple times by the APSX pages? Forget the fact the code might not be perfect - only that
I would like to arrange my code this way.
I suspect there may be caveats - but I need a more knowledgeable opinion.
Public Class MyUtils
Public Shared Function FillList(ByVal objList As DropDownList, ByVal
sSql As String, ByVal sConnection As String) As Boolean
Dim dr As OleDb.OleDbDataReader, Li As ListItem
Dim cn As New OleDb.OleDbConnection(sConnection)
Dim cmd As OleDb.OleDbCommand
Try
cn.Open()
cmd = New OleDb.OleDbCommand(sSql, cn)
dr = cmd.ExecuteReader(CommandBehavior.CloseConnection)
While dr.Read
Li = New ListItem
Li.Text = dr(0)
Li.Value = dr(1)
objList.Items.Add(Li)
End While
Catch ex As Exception
Stop
Return False
Finally
cmd.Dispose()
If dr Is Nothing = False Then dr.Close()
cn.Close()
End Try
Return True
End Function
Public Function EmptyList(...)
...
End Function
...
...
'Other Public Shared Functions...
...
...
End Class
Usage...
FillList(cmbListOfNames,
AppSettings("SQL.PEOPLE"),AppSettings("CONSTRING.M ANAGEMENT"))
Looks good to me. Just the sort of helper function you might want to use in
a variety of apps without necessarily instantiating an object to do it.
--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.
"Stevie_mac" <no******@please.com> wrote in message
news:e1**************@TK2MSFTNGP10.phx.gbl... Hi all, quick question - I need a bit of clarity.
If I have a public class with only Public Shared functions in it, in an
APS.NET web app (for common procedures) is it safe (since multiple web pages, can at any time access the code within)
The reason for a Shared class like this is that, it would contain all of
the useful functions we put together over time like FillList, SelectListItem, FindLastItemInList, EmptyList, SortList etc
etc etc
Example below - a simple routine that fills a dropdownlist. Would it be
safe being accessed at multiple times by the APSX pages? Forget the fact the code might not be perfect - only that
I would like to arrange my code this way.
I suspect there may be caveats - but I need a more knowledgeable opinion.
Public Class MyUtils
Public Shared Function FillList(ByVal objList As DropDownList, ByVal
sSql As String, ByVal sConnection As String) As Boolean
Dim dr As OleDb.OleDbDataReader, Li As ListItem
Dim cn As New OleDb.OleDbConnection(sConnection)
Dim cmd As OleDb.OleDbCommand
Try
cn.Open()
cmd = New OleDb.OleDbCommand(sSql, cn)
dr = cmd.ExecuteReader(CommandBehavior.CloseConnection)
While dr.Read
Li = New ListItem
Li.Text = dr(0)
Li.Value = dr(1)
objList.Items.Add(Li)
End While
Catch ex As Exception
Stop
Return False
Finally
cmd.Dispose()
If dr Is Nothing = False Then dr.Close()
cn.Close()
End Try
Return True
End Function
Public Function EmptyList(...)
...
End Function
...
...
'Other Public Shared Functions...
...
...
End Class
Usage...
FillList(cmbListOfNames,
AppSettings("SQL.PEOPLE"),AppSettings("CONSTRING.M ANAGEMENT"))
Looks good to me. Just the sort of helper function you might want to use in
a variety of apps without necessarily instantiating an object to do it.
--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.
"Stevie_mac" <no******@please.com> wrote in message
news:e1**************@TK2MSFTNGP10.phx.gbl... Hi all, quick question - I need a bit of clarity.
If I have a public class with only Public Shared functions in it, in an
APS.NET web app (for common procedures) is it safe (since multiple web pages, can at any time access the code within)
The reason for a Shared class like this is that, it would contain all of
the useful functions we put together over time like FillList, SelectListItem, FindLastItemInList, EmptyList, SortList etc
etc etc
Example below - a simple routine that fills a dropdownlist. Would it be
safe being accessed at multiple times by the APSX pages? Forget the fact the code might not be perfect - only that
I would like to arrange my code this way.
I suspect there may be caveats - but I need a more knowledgeable opinion.
Public Class MyUtils
Public Shared Function FillList(ByVal objList As DropDownList, ByVal
sSql As String, ByVal sConnection As String) As Boolean
Dim dr As OleDb.OleDbDataReader, Li As ListItem
Dim cn As New OleDb.OleDbConnection(sConnection)
Dim cmd As OleDb.OleDbCommand
Try
cn.Open()
cmd = New OleDb.OleDbCommand(sSql, cn)
dr = cmd.ExecuteReader(CommandBehavior.CloseConnection)
While dr.Read
Li = New ListItem
Li.Text = dr(0)
Li.Value = dr(1)
objList.Items.Add(Li)
End While
Catch ex As Exception
Stop
Return False
Finally
cmd.Dispose()
If dr Is Nothing = False Then dr.Close()
cn.Close()
End Try
Return True
End Function
Public Function EmptyList(...)
...
End Function
...
...
'Other Public Shared Functions...
...
...
End Class
Usage...
FillList(cmbListOfNames,
AppSettings("SQL.PEOPLE"),AppSettings("CONSTRING.M ANAGEMENT"))
Well, this might not directly be the answer you're looking for, but...
This looks like routines I've seen that are used populate dropdowns in
original ASP. If you are coming from ASP you may want to resist using
your experiences in ASP.NET.
I think that you'll find yourself binding datasources to dropdowns
rather than populating them this way.
I do have instances where I pass a dropdown to a shared function, and it
works fine, but this is for a specific
business purpose and not for generic processing.
Jim
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
Well, this might not directly be the answer you're looking for, but...
This looks like routines I've seen that are used populate dropdowns in
original ASP. If you are coming from ASP you may want to resist using
your experiences in ASP.NET.
I think that you'll find yourself binding datasources to dropdowns
rather than populating them this way.
I do have instances where I pass a dropdown to a shared function, and it
works fine, but this is for a specific
business purpose and not for generic processing.
Jim
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
Stevie_mac wrote: Hi all, quick question - I need a bit of clarity.
If I have a public class with only Public Shared functions in it, in an APS.NET web app (for common procedures) is it
safe (since multiple web pages, can at any time access the code within)
The reason for a Shared class like this is that, it would contain all of the useful functions we put together over time
like FillList, SelectListItem, FindLastItemInList, EmptyList, SortList etc etc etc
Example below - a simple routine that fills a dropdownlist. Would it be safe being accessed at multiple times by
the APSX pages? Forget the fact the code might not be perfect - only that I would like to arrange my code this way.
As long as the shared functions do not modify shared data, then having
multiple ASPX pages use the functions concurrently should pose no problem.
If they do access shared data (and it's going to be modified), then
you'd need to protect access to the shared data using a Monitor object
(the SyncLock statement in VB.NET or the lock keyword in C#).
It looks like the sample routine you provided should have no problems
with concurrent use.
I suspect there may be caveats - but I need a more knowledgeable opinion.
Public Class MyUtils
Public Shared Function FillList(ByVal objList As DropDownList, ByVal sSql As String, ByVal sConnection As String) As
Boolean
Dim dr As OleDb.OleDbDataReader, Li As ListItem
Dim cn As New OleDb.OleDbConnection(sConnection)
Dim cmd As OleDb.OleDbCommand
Try
cn.Open()
cmd = New OleDb.OleDbCommand(sSql, cn)
dr = cmd.ExecuteReader(CommandBehavior.CloseConnection)
While dr.Read
Li = New ListItem
Li.Text = dr(0)
Li.Value = dr(1)
objList.Items.Add(Li)
End While
Catch ex As Exception
Stop
Return False
Finally
cmd.Dispose()
If dr Is Nothing = False Then dr.Close()
cn.Close()
End Try
Return True
End Function
Public Function EmptyList(...)
...
End Function
...
...
'Other Public Shared Functions...
...
...
End Class
Usage...
FillList(cmbListOfNames, AppSettings("SQL.PEOPLE"),AppSettings("CONSTRING.M ANAGEMENT"))
--
mikeb
Stevie_mac wrote: Hi all, quick question - I need a bit of clarity.
If I have a public class with only Public Shared functions in it, in an APS.NET web app (for common procedures) is it
safe (since multiple web pages, can at any time access the code within)
The reason for a Shared class like this is that, it would contain all of the useful functions we put together over time
like FillList, SelectListItem, FindLastItemInList, EmptyList, SortList etc etc etc
Example below - a simple routine that fills a dropdownlist. Would it be safe being accessed at multiple times by
the APSX pages? Forget the fact the code might not be perfect - only that I would like to arrange my code this way.
As long as the shared functions do not modify shared data, then having
multiple ASPX pages use the functions concurrently should pose no problem.
If they do access shared data (and it's going to be modified), then
you'd need to protect access to the shared data using a Monitor object
(the SyncLock statement in VB.NET or the lock keyword in C#).
It looks like the sample routine you provided should have no problems
with concurrent use.
I suspect there may be caveats - but I need a more knowledgeable opinion.
Public Class MyUtils
Public Shared Function FillList(ByVal objList As DropDownList, ByVal sSql As String, ByVal sConnection As String) As
Boolean
Dim dr As OleDb.OleDbDataReader, Li As ListItem
Dim cn As New OleDb.OleDbConnection(sConnection)
Dim cmd As OleDb.OleDbCommand
Try
cn.Open()
cmd = New OleDb.OleDbCommand(sSql, cn)
dr = cmd.ExecuteReader(CommandBehavior.CloseConnection)
While dr.Read
Li = New ListItem
Li.Text = dr(0)
Li.Value = dr(1)
objList.Items.Add(Li)
End While
Catch ex As Exception
Stop
Return False
Finally
cmd.Dispose()
If dr Is Nothing = False Then dr.Close()
cn.Close()
End Try
Return True
End Function
Public Function EmptyList(...)
...
End Function
...
...
'Other Public Shared Functions...
...
...
End Class
Usage...
FillList(cmbListOfNames, AppSettings("SQL.PEOPLE"),AppSettings("CONSTRING.M ANAGEMENT"))
--
mikeb
Thanks every one for taking the rime to respond.
All your answers were in part, the whole answer i was looking for.
My main concern was not fully unsderstanding VB shared - was cleared up nicely by mikeb
<quote>
If they do access shared data (and it's going to be modified), then
you'd need to protect access to the shared data using a Monitor object
(the SyncLock statement in VB.NET or the lock keyword in C#).
</quote>
but equally, there was some good ideas in the others
Yes data binding is 'the way' (i do do it some if Im coding for myself) but there is times when you need to loop it!
As for inheriting my own 'webpage' with protected members - this is a good idea & more OOP solution, however, one would
have to modify existing code rather than *modify* (sounds like my current role - 'The modifier') ;-) But I do agree,
this is probably the better solution if starting a new.
Thanks every one for taking the rime to respond.
All your answers were in part, the whole answer i was looking for.
My main concern was not fully unsderstanding VB shared - was cleared up nicely by mikeb
<quote>
If they do access shared data (and it's going to be modified), then
you'd need to protect access to the shared data using a Monitor object
(the SyncLock statement in VB.NET or the lock keyword in C#).
</quote>
but equally, there was some good ideas in the others
Yes data binding is 'the way' (i do do it some if Im coding for myself) but there is times when you need to loop it!
As for inheriting my own 'webpage' with protected members - this is a good idea & more OOP solution, however, one would
have to modify existing code rather than *modify* (sounds like my current role - 'The modifier') ;-) But I do agree,
this is probably the better solution if starting a new.
Hi MikeB
Stevie answered me in another newsgroup on my question why his class should
be shared, that you told him with that this was OK. Which for me also
implements the best way to go.
His class contents as far as I can see only everytime new build objects or
uses objects which are given to the procedure by reference or value.
Therefore I do not understand it why it is OK (the best way to go) to do
that in a shared class, maybe you can explain it for me?
Or do you mean it will run and most probably give no errors?
Cor
Hi MikeB
Stevie answered me in another newsgroup on my question why his class should
be shared, that you told him with that this was OK. Which for me also
implements the best way to go.
His class contents as far as I can see only everytime new build objects or
uses objects which are given to the procedure by reference or value.
Therefore I do not understand it why it is OK (the best way to go) to do
that in a shared class, maybe you can explain it for me?
Or do you mean it will run and most probably give no errors?
Cor
Hello again Cor,
In our other thread, I was a bit off your track of thought, I understand now why you question this...
The use of share class VS instantiating an object is (almost) completely a matter of programmatic simplicity. I do agree
that a class with members that are created once & reused is the most obvious choice - in most cases, however, in ASP.NET
(web) programming, every call to a page is a new object anyway (yes I could use Session but nature of the work I'm doing
means the users would suffer timeouts). Not to say that the structure of what I'm currently working on couldn't be
arranged so that the use on instantiated classes with member variables stored Session was viable (I.E. previous input
was stored in Viewstate & Session objects rebuilt from it when timed out) but there are arguments against this.
Besides, that function (one of quite a few) was probably the worst example! most of the functions would be rather benign
(like Empty, FindInListByValue, Shortlist)
Anyway, my initial question was really to better understand VB Shared key word, which I now do.
Thanks again, stevie_mac
"Cor Ligthert" <no**********@planet.nl> wrote in message news:%2***************@tk2msftngp13.phx.gbl... Hi MikeB
Stevie answered me in another newsgroup on my question why his class should
be shared, that you told him with that this was OK. Which for me also
implements the best way to go.
His class contents as far as I can see only everytime new build objects or
uses objects which are given to the procedure by reference or value.
Therefore I do not understand it why it is OK (the best way to go) to do
that in a shared class, maybe you can explain it for me?
Or do you mean it will run and most probably give no errors?
Cor
Hello again Cor,
In our other thread, I was a bit off your track of thought, I understand now why you question this...
The use of share class VS instantiating an object is (almost) completely a matter of programmatic simplicity. I do agree
that a class with members that are created once & reused is the most obvious choice - in most cases, however, in ASP.NET
(web) programming, every call to a page is a new object anyway (yes I could use Session but nature of the work I'm doing
means the users would suffer timeouts). Not to say that the structure of what I'm currently working on couldn't be
arranged so that the use on instantiated classes with member variables stored Session was viable (I.E. previous input
was stored in Viewstate & Session objects rebuilt from it when timed out) but there are arguments against this.
Besides, that function (one of quite a few) was probably the worst example! most of the functions would be rather benign
(like Empty, FindInListByValue, Shortlist)
Anyway, my initial question was really to better understand VB Shared key word, which I now do.
Thanks again, stevie_mac
"Cor Ligthert" <no**********@planet.nl> wrote in message news:%2***************@tk2msftngp13.phx.gbl... Hi MikeB
Stevie answered me in another newsgroup on my question why his class should
be shared, that you told him with that this was OK. Which for me also
implements the best way to go.
His class contents as far as I can see only everytime new build objects or
uses objects which are given to the procedure by reference or value.
Therefore I do not understand it why it is OK (the best way to go) to do
that in a shared class, maybe you can explain it for me?
Or do you mean it will run and most probably give no errors?
Cor
Cor Ligthert wrote: Hi MikeB
Stevie answered me in another newsgroup on my question why his class should
be shared, that you told him with that this was OK. Which for me also
implements the best way to go.
If I recall correctly, I was focusing on stevie_mac's question about the
*safety* of a shared method being accessed by multiple ASPX pages. I
really didn't look at whether his routine should be shared versus being
an instance method.
As far as the 'best' way to go, I think I'd agree with Jim Corey's
response that stevie_mac should look at databinding.
His class contents as far as I can see only everytime new build objects or
uses objects which are given to the procedure by reference or value.
Therefore I do not understand it why it is OK (the best way to go) to do
that in a shared class, maybe you can explain it for me?
The difference between a shared method and an instance method is that a
shared method does not get an implicit object instance to work on - it
can only work on the items passed to it in the parameter list or on
shared data that also does not belong to an object instance.
Some of the times that you might want to use shared methods are:
1) you want to have a method work on an existing class, but the
class is sealed so you can't derive a new class from it. You see this
type of shared method all the time for handling strings.
2) you want a method that can deal with objects of various classes
that might not be in the same hierarchy. The Convert class is an example
of this.
3) you want a factory method that creates or finds an object
instance and returns it (like the Singleton pattern).
Or do you mean it will run and most probably give no errors?
--
mikeb
Cor Ligthert wrote: Hi MikeB
Stevie answered me in another newsgroup on my question why his class should
be shared, that you told him with that this was OK. Which for me also
implements the best way to go.
If I recall correctly, I was focusing on stevie_mac's question about the
*safety* of a shared method being accessed by multiple ASPX pages. I
really didn't look at whether his routine should be shared versus being
an instance method.
As far as the 'best' way to go, I think I'd agree with Jim Corey's
response that stevie_mac should look at databinding.
His class contents as far as I can see only everytime new build objects or
uses objects which are given to the procedure by reference or value.
Therefore I do not understand it why it is OK (the best way to go) to do
that in a shared class, maybe you can explain it for me?
The difference between a shared method and an instance method is that a
shared method does not get an implicit object instance to work on - it
can only work on the items passed to it in the parameter list or on
shared data that also does not belong to an object instance.
Some of the times that you might want to use shared methods are:
1) you want to have a method work on an existing class, but the
class is sealed so you can't derive a new class from it. You see this
type of shared method all the time for handling strings.
2) you want a method that can deal with objects of various classes
that might not be in the same hierarchy. The Convert class is an example
of this.
3) you want a factory method that creates or finds an object
instance and returns it (like the Singleton pattern).
Or do you mean it will run and most probably give no errors?
--
mikeb This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: William C. White |
last post by:
Does anyone know of a way to use PHP /w Authorize.net AIM without using
cURL? Our website is hosted on a shared drive and the webhost company
doesn't installed additional software (such as cURL)...
|
by: Albert Ahtenberg |
last post by:
Hello,
I don't know if it is only me but I was sure that header("Location:url")
redirects the browser instantly to URL, or at least stops the execution of
the code. But appearantely it continues...
|
by: James |
last post by:
Hi,
I have a form with 2 fields.
'A'
'B'
The user completes one of the fields and the form is submitted.
On the results page I want to run a query, but this will change
subject to which...
|
by: Ollivier Robert |
last post by:
Hello,
I'm trying to link PHP with Oracle 9.2.0/OCI8 with gcc 3.2.3 on a Solaris9
system. The link succeeds but everytime I try to run php, I get a SEGV from
inside the libcnltsh.so library.
...
|
by: Richard Galli |
last post by:
I want viewers to compare state laws on a single subject.
Imagine a three-column table with a drop-down box on the top. A viewer
selects a state from the list, and that state's text fills the...
|
by: Albert Ahtenberg |
last post by:
Hello,
I have two questions.
1. When the user presses the back button and returns to a form he filled
the form is reseted. How do I leave there the values he inserted?
2. When the...
|
by: inderjit S Gabrie |
last post by:
Hi all
Here is the scenerio ...is it possibly to do this...
i am getting valid course dates output on to a web which i have designed
....all is okay so far , look at the following web url
...
|
by: Jack |
last post by:
Hi All,
What is the PHP equivilent of Oracle bind variables in a SQL statement, e.g.
select x from y where z=:parameter
Which in asp/jsp would be followed by some statements to bind a value...
|
by: Sandwick |
last post by:
I am trying to change the size of a drawing so they are all 3x3.
the script below is what i was trying to use to cut it in half ... I
get errors.
I can display the normal picture but not the...
|
by: Charles Arthur |
last post by:
How do i turn on java script on a villaon, callus and itel keypad mobile phone
|
by: BarryA |
last post by:
What are the essential steps and strategies outlined in the Data Structures and Algorithms (DSA) roadmap for aspiring data scientists? How can individuals effectively utilize this roadmap to progress...
|
by: Sonnysonu |
last post by:
This is the data of csv file
1 2 3
1 2 3
1 2 3
1 2 3
2 3
2 3
3
the lengths should be different i have to store the data by column-wise with in the specific length.
suppose the i have to...
|
by: Hystou |
last post by:
There are some requirements for setting up RAID:
1. The motherboard and BIOS support RAID configuration.
2. The motherboard has 2 or more available SATA protocol SSD/HDD slots (including MSATA, M.2...
|
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: Oralloy |
last post by:
Hello folks,
I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>".
The problem is that using the GNU compilers,...
|
by: jinu1996 |
last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven...
|
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...
| |
