Consider the following code that adds a table to a DataSet dynamically:
<script runat="server">
Sub Page_Load(ByVal obj As Object, ByVal ea As EventArgs)
'Create an empty DataSet
Dim dSet As New DataSet
'Create a new table & add columns
Dim dTable As New DataTable("User s")
dTable.Columns. Add("ID", Type.GetType("S ystem.Int32"))
dTable.Columns. Add("First Name", Type.GetType("S ystem.String"))
dTable.Columns. Add("Last Name", Type.GetType("S ystem.String"))
dSet.Tables.Add (dTable)
'Define the Primary Key
Dim dColumn() As DataColumn =
{dSet.Tables("U sers").Columns( "ID")}
dSet.Tables("Us ers").PrimaryKe y = dColumn
End Sub
</script>
The above code works fine but if the column named "ID" is set as the
Primary Key before adding the DataTable to the DataSet i.e. if the 2
lines preceding the "End Sub" line are cut & pasted just above the line
"dSet.Tables.Ad d(dTable)", then the following error gets generated:
Object reference not set to an instance of an object.
pointing to the line
Dim dColumn() As DataColumn = {dSet.Tables("U sers").Columns( "ID")}
Which "object" is the above error message referring to? Is it the
DataSet or the DataTable or some other object? Also is the error
generating because I am defining the column "ID" as the Primary Key
before adding the DataTable to the DataSet? If yes, then why should
this cause the error? After all, I am defining the Primary Key after
creating the DataTable i.e. the schema of the DataTable is ready after
which only I am defining the Primary Key, isn't it? So why the error?
Thanks,
Arpan
10  3878 
These are the culprits:
dTable.Columns. Add("ID", Type.GetType("S ystem.Int32"))
dTable.Columns. Add("First Name", Type.GetType("S ystem.String"))
dTable.Columns. Add("Last Name", Type.GetType("S ystem.String"))
You don't have any actual DataColumns in existence yet, so how can you add
what you don't have to the Columns collection of dTable?
Should be:
dTable.Columns. Add(New DataColumn("ID" ,
Type.GetType("S ystem.Int32")))
dTable.Columns. Add(New DataColumn("Fir st Name",
Type.GetType("S ystem.String")) )
dTable.Columns. Add(New DataColumn("Las t Name",
Type.GetType("S ystem.String")) )
"Arpan" <ar******@hotma il.comwrote in message
news:11******** **************@ p79g2000cwp.goo glegroups.com.. .
Consider the following code that adds a table to a DataSet dynamically:
<script runat="server">
Sub Page_Load(ByVal obj As Object, ByVal ea As EventArgs)
'Create an empty DataSet
Dim dSet As New DataSet
'Create a new table & add columns
Dim dTable As New DataTable("User s")
dTable.Columns. Add("ID", Type.GetType("S ystem.Int32"))
dTable.Columns. Add("First Name", Type.GetType("S ystem.String"))
dTable.Columns. Add("Last Name", Type.GetType("S ystem.String"))
dSet.Tables.Add (dTable)
'Define the Primary Key
Dim dColumn() As DataColumn =
{dSet.Tables("U sers").Columns( "ID")}
dSet.Tables("Us ers").PrimaryKe y = dColumn
End Sub
</script>
The above code works fine but if the column named "ID" is set as the
Primary Key before adding the DataTable to the DataSet i.e. if the 2
lines preceding the "End Sub" line are cut & pasted just above the line
"dSet.Tables.Ad d(dTable)", then the following error gets generated:
Object reference not set to an instance of an object.
pointing to the line
Dim dColumn() As DataColumn = {dSet.Tables("U sers").Columns( "ID")}
Which "object" is the above error message referring to? Is it the
DataSet or the DataTable or some other object? Also is the error
generating because I am defining the column "ID" as the Primary Key
before adding the DataTable to the DataSet? If yes, then why should
this cause the error? After all, I am defining the Primary Key after
creating the DataTable i.e. the schema of the DataTable is ready after
which only I am defining the Primary Key, isn't it? So why the error?
Thanks,
Arpan
Scott, you mean to say that the following lines
dTable.Columns. Add("ID", Type.GetType("S ystem.Int32"))
dTable.Columns. Add("First Name", Type.GetType("S ystem.String"))
dTable.Columns. Add("Last Name", Type.GetType("S ystem.String"))
in reality, DO NOT create the columns "ID, "First Name" & "Last Name"
in the DataTable in the first place? But if that's the case, I haven't
used "New DataColumn" anywhere in the code I have cited in post #1 but
the DataGrid does display all the columns & the rows correctly when the
code is executed. How come?
Moreover, if the above 3 lines do not create any columns, when do they
get created in the code shown in post #1? In other words, which line in
the code in post #1 actually creates the 3 columns?
Finally, even if I replace the above 3 lines with the 3 lines you have
shown & set the Primary Key on the column "ID" before adding the
DataTable to the DataSet, then still the "Object reference not set to
an instance of an object" gets thrown. Why?
Thanks,
Regards,
Arpan
Scott M. wrote:
These are the culprits:
dTable.Columns. Add("ID", Type.GetType("S ystem.Int32"))
dTable.Columns. Add("First Name", Type.GetType("S ystem.String"))
dTable.Columns. Add("Last Name", Type.GetType("S ystem.String"))
You don't have any actual DataColumns in existence yet, so how can you add
what you don't have to the Columns collection of dTable?
Should be:
dTable.Columns. Add(New DataColumn("ID" ,
Type.GetType("S ystem.Int32")))
dTable.Columns. Add(New DataColumn("Fir st Name",
Type.GetType("S ystem.String")) )
dTable.Columns. Add(New DataColumn("Las t Name",
Type.GetType("S ystem.String")) )
"Arpan" <ar******@hotma il.comwrote in message
news:11******** **************@ p79g2000cwp.goo glegroups.com.. .
Consider the following code that adds a table to a DataSet dynamically:
<script runat="server">
Sub Page_Load(ByVal obj As Object, ByVal ea As EventArgs)
'Create an empty DataSet
Dim dSet As New DataSet
'Create a new table & add columns
Dim dTable As New DataTable("User s")
dTable.Columns. Add("ID", Type.GetType("S ystem.Int32"))
dTable.Columns. Add("First Name", Type.GetType("S ystem.String"))
dTable.Columns. Add("Last Name", Type.GetType("S ystem.String"))
dSet.Tables.Add (dTable)
'Define the Primary Key
Dim dColumn() As DataColumn =
{dSet.Tables("U sers").Columns( "ID")}
dSet.Tables("Us ers").PrimaryKe y = dColumn
End Sub
</script>
The above code works fine but if the column named "ID" is set as the
Primary Key before adding the DataTable to the DataSet i.e. if the 2
lines preceding the "End Sub" line are cut & pasted just above the line
"dSet.Tables.Ad d(dTable)", then the following error gets generated:
Object reference not set to an instance of an object.
pointing to the line
Dim dColumn() As DataColumn = {dSet.Tables("U sers").Columns( "ID")}
Which "object" is the above error message referring to? Is it the
DataSet or the DataTable or some other object? Also is the error
generating because I am defining the column "ID" as the Primary Key
before adding the DataTable to the DataSet? If yes, then why should
this cause the error? After all, I am defining the Primary Key after
creating the DataTable i.e. the schema of the DataTable is ready after
which only I am defining the Primary Key, isn't it? So why the error?
Thanks,
Arpan
Ok, first of all if you attempt to set your primary key like this:
'Define the Primary Key
Dim dColumn As DataColumn() = {dSet.Tables("U sers").Columns( "ID")}
dSet.Tables("Us ers").PrimaryKe y = dColumn
dSet.Tables.Add (dTable)
You'll get the object reference error because you are going into the dataset
and looking for table "Users" before you've added it to the dataset in the
first place.
As for the creation of the columns without instantiating them (as I showed
in my last post), I can't explain why it works for you. The columns must be
getting created by implicit means. Nonetheless, it is better practice to
explicitly create the columns ahead of time :
'Create an empty DataSet
Dim dSet As New DataSet
'Create a new table & add columns
Dim dTable As New DataTable("User s")
Dim idCol As New DataColumn("ID" , Type.GetType("S ystem.Int32"))
Dim fNameCol As New DataColumn("Fir st Name", Type.GetType("S ystem.String"))
Dim lNameCol As New DataColumn("Las t Name", Type.GetType("S ystem.String"))
dTable.Columns. Add(idCol)
dTable.Columns. Add(fNameCol)
dTable.Columns. Add(lNameCol)
dSet.Tables.Add (dTable)
'Define the Primary Key
Dim dColumn As DataColumn() = {dSet.Tables("U sers").Columns( "ID")}
dSet.Tables("Us ers").PrimaryKe y = dColumn
"Arpan" <ar******@hotma il.comwrote in message
news:11******** **************@ 75g2000cwc.goog legroups.com...
Scott, you mean to say that the following lines
dTable.Columns. Add("ID", Type.GetType("S ystem.Int32"))
dTable.Columns. Add("First Name", Type.GetType("S ystem.String"))
dTable.Columns. Add("Last Name", Type.GetType("S ystem.String"))
in reality, DO NOT create the columns "ID, "First Name" & "Last Name"
in the DataTable in the first place? But if that's the case, I haven't
used "New DataColumn" anywhere in the code I have cited in post #1 but
the DataGrid does display all the columns & the rows correctly when the
code is executed. How come?
Moreover, if the above 3 lines do not create any columns, when do they
get created in the code shown in post #1? In other words, which line in
the code in post #1 actually creates the 3 columns?
Finally, even if I replace the above 3 lines with the 3 lines you have
shown & set the Primary Key on the column "ID" before adding the
DataTable to the DataSet, then still the "Object reference not set to
an instance of an object" gets thrown. Why?
Thanks,
Regards,
Arpan
Scott M. wrote:
>These are the culprits:
dTable.Columns. Add("ID", Type.GetType("S ystem.Int32"))
dTable.Columns. Add("First Name", Type.GetType("S ystem.String"))
dTable.Columns. Add("Last Name", Type.GetType("S ystem.String"))
You don't have any actual DataColumns in existence yet, so how can you
add
what you don't have to the Columns collection of dTable?
Should be:
dTable.Columns. Add(New DataColumn("ID" ,
Type.GetType(" System.Int32")) )
dTable.Columns. Add(New DataColumn("Fir st Name",
Type.GetType(" System.String") ))
dTable.Columns. Add(New DataColumn("Las t Name",
Type.GetType(" System.String") ))
"Arpan" <ar******@hotma il.comwrote in message
news:11******* *************** @p79g2000cwp.go oglegroups.com. ..
Consider the following code that adds a table to a DataSet dynamically:
<script runat="server">
Sub Page_Load(ByVal obj As Object, ByVal ea As EventArgs)
'Create an empty DataSet
Dim dSet As New DataSet
'Create a new table & add columns
Dim dTable As New DataTable("User s")
dTable.Columns. Add("ID", Type.GetType("S ystem.Int32"))
dTable.Columns. Add("First Name", Type.GetType("S ystem.String"))
dTable.Columns. Add("Last Name", Type.GetType("S ystem.String"))
dSet.Tables.Add (dTable)
'Define the Primary Key
Dim dColumn() As DataColumn =
{dSet.Tables("U sers").Columns( "ID")}
dSet.Tables("Us ers").PrimaryKe y = dColumn
End Sub
</script>
The above code works fine but if the column named "ID" is set as the
Primary Key before adding the DataTable to the DataSet i.e. if the 2
lines preceding the "End Sub" line are cut & pasted just above the line
"dSet.Tables.Ad d(dTable)", then the following error gets generated:
Object reference not set to an instance of an object.
pointing to the line
Dim dColumn() As DataColumn = {dSet.Tables("U sers").Columns( "ID")}
Which "object" is the above error message referring to? Is it the
DataSet or the DataTable or some other object? Also is the error
generating because I am defining the column "ID" as the Primary Key
before adding the DataTable to the DataSet? If yes, then why should
this cause the error? After all, I am defining the Primary Key after
creating the DataTable i.e. the schema of the DataTable is ready after
which only I am defining the Primary Key, isn't it? So why the error?
Thanks,
Arpan
Thanks, Scott, for the suggestions. You have indeed made it easier for
me to grasp this topic & the reason behind the error message. Moreover,
I have always preferred coding in the manner you have shown & not club
2 lines into one which can be very well done in ASP.NET. I believe it
makes things easier to understand especially for newbies like me.
>The columns must be getting created by implicit means
That was my first impression.
One last question (probably!) on this topic - can the Primary Key be
defined on the "ID" column before adding the DataTable to the DataSet?
If yes, then how?
Thanks once again for your helpful advices.
Regards,
Arpan
Scott M. wrote:
Ok, first of all if you attempt to set your primary key like this:
'Define the Primary Key
Dim dColumn As DataColumn() = {dSet.Tables("U sers").Columns( "ID")}
dSet.Tables("Us ers").PrimaryKe y = dColumn
dSet.Tables.Add (dTable)
You'll get the object reference error because you are going into the dataset
and looking for table "Users" before you've added it to the dataset in the
first place.
As for the creation of the columns without instantiating them (as I showed
in my last post), I can't explain why it works for you. The columns must be
getting created by implicit means. Nonetheless, it is better practice to
explicitly create the columns ahead of time :
'Create an empty DataSet
Dim dSet As New DataSet
'Create a new table & add columns
Dim dTable As New DataTable("User s")
Dim idCol As New DataColumn("ID" , Type.GetType("S ystem.Int32"))
Dim fNameCol As New DataColumn("Fir st Name", Type.GetType("S ystem.String"))
Dim lNameCol As New DataColumn("Las t Name", Type.GetType("S ystem.String"))
dTable.Columns. Add(idCol)
dTable.Columns. Add(fNameCol)
dTable.Columns. Add(lNameCol)
dSet.Tables.Add (dTable)
'Define the Primary Key
Dim dColumn As DataColumn() = {dSet.Tables("U sers").Columns( "ID")}
dSet.Tables("Us ers").PrimaryKe y = dColumn
"Arpan" <ar******@hotma il.comwrote in message
news:11******** **************@ 75g2000cwc.goog legroups.com...
Scott, you mean to say that the following lines
dTable.Columns. Add("ID", Type.GetType("S ystem.Int32"))
dTable.Columns. Add("First Name", Type.GetType("S ystem.String"))
dTable.Columns. Add("Last Name", Type.GetType("S ystem.String"))
in reality, DO NOT create the columns "ID, "First Name" & "Last Name"
in the DataTable in the first place? But if that's the case, I haven't
used "New DataColumn" anywhere in the code I have cited in post #1 but
the DataGrid does display all the columns & the rows correctly when the
code is executed. How come?
Moreover, if the above 3 lines do not create any columns, when do they
get created in the code shown in post #1? In other words, which line in
the code in post #1 actually creates the 3 columns?
Finally, even if I replace the above 3 lines with the 3 lines you have
shown & set the Primary Key on the column "ID" before adding the
DataTable to the DataSet, then still the "Object reference not set to
an instance of an object" gets thrown. Why?
Thanks,
Regards,
Arpan
Scott M. wrote:
These are the culprits:
dTable.Columns. Add("ID", Type.GetType("S ystem.Int32"))
dTable.Columns. Add("First Name", Type.GetType("S ystem.String"))
dTable.Columns. Add("Last Name", Type.GetType("S ystem.String"))
You don't have any actual DataColumns in existence yet, so how can you
add
what you don't have to the Columns collection of dTable?
Should be:
dTable.Columns. Add(New DataColumn("ID" ,
Type.GetType("S ystem.Int32")))
dTable.Columns. Add(New DataColumn("Fir st Name",
Type.GetType("S ystem.String")) )
dTable.Columns. Add(New DataColumn("Las t Name",
Type.GetType("S ystem.String")) )
"Arpan" <ar******@hotma il.comwrote in message
news:11******** **************@ p79g2000cwp.goo glegroups.com.. .
Consider the following code that adds a table to a DataSet dynamically:
<script runat="server">
Sub Page_Load(ByVal obj As Object, ByVal ea As EventArgs)
'Create an empty DataSet
Dim dSet As New DataSet
'Create a new table & add columns
Dim dTable As New DataTable("User s")
dTable.Columns. Add("ID", Type.GetType("S ystem.Int32"))
dTable.Columns. Add("First Name", Type.GetType("S ystem.String"))
dTable.Columns. Add("Last Name", Type.GetType("S ystem.String"))
dSet.Tables.Add (dTable)
'Define the Primary Key
Dim dColumn() As DataColumn =
{dSet.Tables("U sers").Columns( "ID")}
dSet.Tables("Us ers").PrimaryKe y = dColumn
End Sub
</script>
The above code works fine but if the column named "ID" is set as the
Primary Key before adding the DataTable to the DataSet i.e. if the 2
lines preceding the "End Sub" line are cut & pasted just above the line
"dSet.Tables.Ad d(dTable)", then the following error gets generated:
Object reference not set to an instance of an object.
pointing to the line
Dim dColumn() As DataColumn = {dSet.Tables("U sers").Columns( "ID")}
Which "object" is the above error message referring to? Is it the
DataSet or the DataTable or some other object? Also is the error
generating because I am defining the column "ID" as the Primary Key
before adding the DataTable to the DataSet? If yes, then why should
this cause the error? After all, I am defining the Primary Key after
creating the DataTable i.e. the schema of the DataTable is ready after
which only I am defining the Primary Key, isn't it? So why the error?
Thanks,
Arpan
Yes, the primary key can be set before the table is added to the dataset.
"Arpan" <ar******@hotma il.comwrote in message
news:11******** **************@ m73g2000cwd.goo glegroups.com.. .
Thanks, Scott, for the suggestions. You have indeed made it easier for
me to grasp this topic & the reason behind the error message. Moreover,
I have always preferred coding in the manner you have shown & not club
2 lines into one which can be very well done in ASP.NET. I believe it
makes things easier to understand especially for newbies like me.
>>The columns must be getting created by implicit means
That was my first impression.
One last question (probably!) on this topic - can the Primary Key be
defined on the "ID" column before adding the DataTable to the DataSet?
If yes, then how?
Thanks once again for your helpful advices.
Regards,
Arpan
Scott M. wrote:
>Ok, first of all if you attempt to set your primary key like this:
'Define the Primary Key
Dim dColumn As DataColumn() = {dSet.Tables("U sers").Columns( "ID")}
dSet.Tables("U sers").PrimaryK ey = dColumn
dSet.Tables.Ad d(dTable)
You'll get the object reference error because you are going into the
dataset
and looking for table "Users" before you've added it to the dataset in
the
first place.
As for the creation of the columns without instantiating them (as I
showed
in my last post), I can't explain why it works for you. The columns must
be
getting created by implicit means. Nonetheless, it is better practice to
explicitly create the columns ahead of time :
'Create an empty DataSet
Dim dSet As New DataSet
'Create a new table & add columns
Dim dTable As New DataTable("User s")
Dim idCol As New DataColumn("ID" , Type.GetType("S ystem.Int32"))
Dim fNameCol As New DataColumn("Fir st Name",
Type.GetType(" System.String") )
Dim lNameCol As New DataColumn("Las t Name",
Type.GetType(" System.String") )
dTable.Columns .Add(idCol)
dTable.Columns .Add(fNameCol)
dTable.Columns .Add(lNameCol)
dSet.Tables.Ad d(dTable)
'Define the Primary Key
Dim dColumn As DataColumn() = {dSet.Tables("U sers").Columns( "ID")}
dSet.Tables("U sers").PrimaryK ey = dColumn
"Arpan" <ar******@hotma il.comwrote in message
news:11******* *************** @75g2000cwc.goo glegroups.com.. .
Scott, you mean to say that the following lines
dTable.Columns. Add("ID", Type.GetType("S ystem.Int32"))
dTable.Columns. Add("First Name", Type.GetType("S ystem.String"))
dTable.Columns. Add("Last Name", Type.GetType("S ystem.String"))
in reality, DO NOT create the columns "ID, "First Name" & "Last Name"
in the DataTable in the first place? But if that's the case, I haven't
used "New DataColumn" anywhere in the code I have cited in post #1 but
the DataGrid does display all the columns & the rows correctly when the
code is executed. How come?
Moreover, if the above 3 lines do not create any columns, when do they
get created in the code shown in post #1? In other words, which line in
the code in post #1 actually creates the 3 columns?
Finally, even if I replace the above 3 lines with the 3 lines you have
shown & set the Primary Key on the column "ID" before adding the
DataTable to the DataSet, then still the "Object reference not set to
an instance of an object" gets thrown. Why?
Thanks,
Regards,
Arpan
Scott M. wrote:
These are the culprits:
dTable.Columns. Add("ID", Type.GetType("S ystem.Int32"))
dTable.Columns. Add("First Name",
Type.GetType(" System.String") )
dTable.Columns. Add("Last Name", Type.GetType("S ystem.String"))
You don't have any actual DataColumns in existence yet, so how can you
add
what you don't have to the Columns collection of dTable?
Should be:
dTable.Columns. Add(New DataColumn("ID" ,
Type.GetType(" System.Int32")) )
dTable.Columns. Add(New DataColumn("Fir st Name",
Type.GetType(" System.String") ))
dTable.Columns. Add(New DataColumn("Las t Name",
Type.GetType(" System.String") ))
"Arpan" <ar******@hotma il.comwrote in message
news:11******* *************** @p79g2000cwp.go oglegroups.com. ..
Consider the following code that adds a table to a DataSet
dynamically:
<script runat="server">
Sub Page_Load(ByVal obj As Object, ByVal ea As EventArgs)
'Create an empty DataSet
Dim dSet As New DataSet
'Create a new table & add columns
Dim dTable As New DataTable("User s")
dTable.Columns. Add("ID", Type.GetType("S ystem.Int32"))
dTable.Columns. Add("First Name",
Type.GetType("S ystem.String"))
dTable.Columns. Add("Last Name",
Type.GetType("S ystem.String"))
dSet.Tables.Add (dTable)
'Define the Primary Key
Dim dColumn() As DataColumn =
{dSet.Tables("U sers").Columns( "ID")}
dSet.Tables("Us ers").PrimaryKe y = dColumn
End Sub
</script>
The above code works fine but if the column named "ID" is set as the
Primary Key before adding the DataTable to the DataSet i.e. if the 2
lines preceding the "End Sub" line are cut & pasted just above the
line
"dSet.Tables.Ad d(dTable)", then the following error gets generated:
Object reference not set to an instance of an object.
pointing to the line
Dim dColumn() As DataColumn = {dSet.Tables("U sers").Columns( "ID")}
Which "object" is the above error message referring to? Is it the
DataSet or the DataTable or some other object? Also is the error
generating because I am defining the column "ID" as the Primary Key
before adding the DataTable to the DataSet? If yes, then why should
this cause the error? After all, I am defining the Primary Key after
creating the DataTable i.e. the schema of the DataTable is ready
after
which only I am defining the Primary Key, isn't it? So why the
error?
Thanks,
Arpan
Yes, the primary key can be set before the table is added to the dataset
How?
Arpan
Scott M. wrote:
Yes, the primary key can be set before the table is added to the dataset.
"Arpan" <ar******@hotma il.comwrote in message
news:11******** **************@ m73g2000cwd.goo glegroups.com.. .
Thanks, Scott, for the suggestions. You have indeed made it easier for
me to grasp this topic & the reason behind the error message. Moreover,
I have always preferred coding in the manner you have shown & not club
2 lines into one which can be very well done in ASP.NET. I believe it
makes things easier to understand especially for newbies like me.
>The columns must be getting created by implicit means
That was my first impression.
One last question (probably!) on this topic - can the Primary Key be
defined on the "ID" column before adding the DataTable to the DataSet?
If yes, then how?
Thanks once again for your helpful advices.
Regards,
Arpan
Scott M. wrote:
Ok, first of all if you attempt to set your primary key like this:
'Define the Primary Key
Dim dColumn As DataColumn() = {dSet.Tables("U sers").Columns( "ID")}
dSet.Tables("Us ers").PrimaryKe y = dColumn
dSet.Tables.Add (dTable)
You'll get the object reference error because you are going into the
dataset
and looking for table "Users" before you've added it to the dataset in
the
first place.
As for the creation of the columns without instantiating them (as I
showed
in my last post), I can't explain why it works for you. The columns must
be
getting created by implicit means. Nonetheless, it is better practice to
explicitly create the columns ahead of time :
'Create an empty DataSet
Dim dSet As New DataSet
'Create a new table & add columns
Dim dTable As New DataTable("User s")
Dim idCol As New DataColumn("ID" , Type.GetType("S ystem.Int32"))
Dim fNameCol As New DataColumn("Fir st Name",
Type.GetType("S ystem.String"))
Dim lNameCol As New DataColumn("Las t Name",
Type.GetType("S ystem.String"))
dTable.Columns. Add(idCol)
dTable.Columns. Add(fNameCol)
dTable.Columns. Add(lNameCol)
dSet.Tables.Add (dTable)
'Define the Primary Key
Dim dColumn As DataColumn() = {dSet.Tables("U sers").Columns( "ID")}
dSet.Tables("Us ers").PrimaryKe y = dColumn
"Arpan" <ar******@hotma il.comwrote in message
news:11******** **************@ 75g2000cwc.goog legroups.com...
Scott, you mean to say that the following lines
dTable.Columns. Add("ID", Type.GetType("S ystem.Int32"))
dTable.Columns. Add("First Name", Type.GetType("S ystem.String"))
dTable.Columns. Add("Last Name", Type.GetType("S ystem.String"))
in reality, DO NOT create the columns "ID, "First Name" & "Last Name"
in the DataTable in the first place? But if that's the case, I haven't
used "New DataColumn" anywhere in the code I have cited in post #1 but
the DataGrid does display all the columns & the rows correctly when the
code is executed. How come?
Moreover, if the above 3 lines do not create any columns, when do they
get created in the code shown in post #1? In other words, which line in
the code in post #1 actually creates the 3 columns?
Finally, even if I replace the above 3 lines with the 3 lines you have
shown & set the Primary Key on the column "ID" before adding the
DataTable to the DataSet, then still the "Object reference not set to
an instance of an object" gets thrown. Why?
Thanks,
Regards,
Arpan
Scott M. wrote:
These are the culprits:
dTable.Columns. Add("ID", Type.GetType("S ystem.Int32"))
dTable.Columns. Add("First Name",
Type.GetType("S ystem.String"))
dTable.Columns. Add("Last Name", Type.GetType("S ystem.String"))
You don't have any actual DataColumns in existence yet, so how can you
add
what you don't have to the Columns collection of dTable?
Should be:
dTable.Columns. Add(New DataColumn("ID" ,
Type.GetType("S ystem.Int32")))
dTable.Columns. Add(New DataColumn("Fir st Name",
Type.GetType("S ystem.String")) )
dTable.Columns. Add(New DataColumn("Las t Name",
Type.GetType("S ystem.String")) )
"Arpan" <ar******@hotma il.comwrote in message
news:11******** **************@ p79g2000cwp.goo glegroups.com.. .
Consider the following code that adds a table to a DataSet
dynamically:
<script runat="server">
Sub Page_Load(ByVal obj As Object, ByVal ea As EventArgs)
'Create an empty DataSet
Dim dSet As New DataSet
'Create a new table & add columns
Dim dTable As New DataTable("User s")
dTable.Columns. Add("ID", Type.GetType("S ystem.Int32"))
dTable.Columns. Add("First Name",
Type.GetType("S ystem.String"))
dTable.Columns. Add("Last Name",
Type.GetType("S ystem.String"))
dSet.Tables.Add (dTable)
'Define the Primary Key
Dim dColumn() As DataColumn =
{dSet.Tables("U sers").Columns( "ID")}
dSet.Tables("Us ers").PrimaryKe y = dColumn
End Sub
</script>
The above code works fine but if the column named "ID" is set as the
Primary Key before adding the DataTable to the DataSet i.e. if the 2
lines preceding the "End Sub" line are cut & pasted just above the
line
"dSet.Tables.Ad d(dTable)", then the following error gets generated:
Object reference not set to an instance of an object.
pointing to the line
Dim dColumn() As DataColumn = {dSet.Tables("U sers").Columns( "ID")}
Which "object" is the above error message referring to? Is it the
DataSet or the DataTable or some other object? Also is the error
generating because I am defining the column "ID" as the Primary Key
before adding the DataTable to the DataSet? If yes, then why should
this cause the error? After all, I am defining the Primary Key after
creating the DataTable i.e. the schema of the DataTable is ready
after
which only I am defining the Primary Key, isn't it? So why the
error?
Thanks,
Arpan
Just think about the objects involved here...The PrimaryKey property is a
property of a DataTable. So, when you want to set that property, you need
to have a DataTable. Now, do you have a DataTable before your DataSet is
all set up, yes, you have dTable. So:
Dim dColumn As DataColumn() = {dTable.Columns ("ID")}
dTable.PrimaryK ey = dColumn
"Arpan" <ar******@hotma il.comwrote in message
news:11******** **************@ b28g2000cwb.goo glegroups.com.. .
>Yes, the primary key can be set before the table is added to the dataset
How?
Arpan
Scott M. wrote:
>Yes, the primary key can be set before the table is added to the dataset.
"Arpan" <ar******@hotma il.comwrote in message
news:11******* *************** @m73g2000cwd.go oglegroups.com. ..
Thanks, Scott, for the suggestions. You have indeed made it easier for
me to grasp this topic & the reason behind the error message. Moreover,
I have always preferred coding in the manner you have shown & not club
2 lines into one which can be very well done in ASP.NET. I believe it
makes things easier to understand especially for newbies like me.
The columns must be getting created by implicit means
That was my first impression.
One last question (probably!) on this topic - can the Primary Key be
defined on the "ID" column before adding the DataTable to the DataSet?
If yes, then how?
Thanks once again for your helpful advices.
Regards,
Arpan
Scott M. wrote:
Ok, first of all if you attempt to set your primary key like this:
'Define the Primary Key
Dim dColumn As DataColumn() = {dSet.Tables("U sers").Columns( "ID")}
dSet.Tables("U sers").PrimaryK ey = dColumn
dSet.Tables.Ad d(dTable)
You'll get the object reference error because you are going into the
dataset
and looking for table "Users" before you've added it to the dataset in
the
first place.
As for the creation of the columns without instantiating them (as I
showed
in my last post), I can't explain why it works for you. The columns
must
be
getting created by implicit means. Nonetheless, it is better practice
to
explicitly create the columns ahead of time :
'Create an empty DataSet
Dim dSet As New DataSet
'Create a new table & add columns
Dim dTable As New DataTable("User s")
Dim idCol As New DataColumn("ID" , Type.GetType("S ystem.Int32"))
Dim fNameCol As New DataColumn("Fir st Name",
Type.GetType(" System.String") )
Dim lNameCol As New DataColumn("Las t Name",
Type.GetType(" System.String") )
dTable.Columns .Add(idCol)
dTable.Columns .Add(fNameCol)
dTable.Columns .Add(lNameCol)
dSet.Tables.Ad d(dTable)
'Define the Primary Key
Dim dColumn As DataColumn() = {dSet.Tables("U sers").Columns( "ID")}
dSet.Tables("U sers").PrimaryK ey = dColumn
"Arpan" <ar******@hotma il.comwrote in message
news:11******* *************** @75g2000cwc.goo glegroups.com.. .
Scott, you mean to say that the following lines
dTable.Columns. Add("ID", Type.GetType("S ystem.Int32"))
dTable.Columns. Add("First Name", Type.GetType("S ystem.String"))
dTable.Columns. Add("Last Name", Type.GetType("S ystem.String"))
in reality, DO NOT create the columns "ID, "First Name" & "Last
Name"
in the DataTable in the first place? But if that's the case, I
haven't
used "New DataColumn" anywhere in the code I have cited in post #1
but
the DataGrid does display all the columns & the rows correctly when
the
code is executed. How come?
Moreover, if the above 3 lines do not create any columns, when do
they
get created in the code shown in post #1? In other words, which line
in
the code in post #1 actually creates the 3 columns?
Finally, even if I replace the above 3 lines with the 3 lines you
have
shown & set the Primary Key on the column "ID" before adding the
DataTable to the DataSet, then still the "Object reference not set
to
an instance of an object" gets thrown. Why?
Thanks,
Regards,
Arpan
Scott M. wrote:
These are the culprits:
dTable.Columns. Add("ID", Type.GetType("S ystem.Int32"))
dTable.Columns. Add("First Name",
Type.GetType(" System.String") )
dTable.Columns. Add("Last Name",
Type.GetType(" System.String") )
You don't have any actual DataColumns in existence yet, so how can
you
add
what you don't have to the Columns collection of dTable?
Should be:
dTable.Columns. Add(New DataColumn("ID" ,
Type.GetType(" System.Int32")) )
dTable.Columns. Add(New DataColumn("Fir st Name",
Type.GetType(" System.String") ))
dTable.Columns. Add(New DataColumn("Las t Name",
Type.GetType(" System.String") ))
"Arpan" <ar******@hotma il.comwrote in message
news:11******* *************** @p79g2000cwp.go oglegroups.com. ..
Consider the following code that adds a table to a DataSet
dynamically:
<script runat="server">
Sub Page_Load(ByVal obj As Object, ByVal ea As EventArgs)
'Create an empty DataSet
Dim dSet As New DataSet
'Create a new table & add columns
Dim dTable As New DataTable("User s")
dTable.Columns. Add("ID", Type.GetType("S ystem.Int32"))
dTable.Columns. Add("First Name",
Type.GetType("S ystem.String"))
dTable.Columns. Add("Last Name",
Type.GetType("S ystem.String"))
dSet.Tables.Add (dTable)
'Define the Primary Key
Dim dColumn() As DataColumn =
{dSet.Tables("U sers").Columns( "ID")}
dSet.Tables("Us ers").PrimaryKe y = dColumn
End Sub
</script>
The above code works fine but if the column named "ID" is set as
the
Primary Key before adding the DataTable to the DataSet i.e. if
the 2
lines preceding the "End Sub" line are cut & pasted just above
the
line
"dSet.Tables.Ad d(dTable)", then the following error gets
generated:
Object reference not set to an instance of an object.
pointing to the line
Dim dColumn() As DataColumn =
{dSet.Tables("U sers").Columns( "ID")}
Which "object" is the above error message referring to? Is it the
DataSet or the DataTable or some other object? Also is the error
generating because I am defining the column "ID" as the Primary
Key
before adding the DataTable to the DataSet? If yes, then why
should
this cause the error? After all, I am defining the Primary Key
after
creating the DataTable i.e. the schema of the DataTable is ready
after
which only I am defining the Primary Key, isn't it? So why the
error?
Thanks,
Arpan
Also, there is no rule that says that a DataTable *must* be added to a
DataSet at all, so setting the primary key must be possible before adding
the table to the DataSet, since you may not even want to use a dataset
anyway.
"Arpan" <ar******@hotma il.comwrote in message
news:11******** **************@ b28g2000cwb.goo glegroups.com.. .
>Yes, the primary key can be set before the table is added to the dataset
How?
Arpan
Scott M. wrote:
>Yes, the primary key can be set before the table is added to the dataset.
"Arpan" <ar******@hotma il.comwrote in message
news:11******* *************** @m73g2000cwd.go oglegroups.com. ..
Thanks, Scott, for the suggestions. You have indeed made it easier for
me to grasp this topic & the reason behind the error message. Moreover,
I have always preferred coding in the manner you have shown & not club
2 lines into one which can be very well done in ASP.NET. I believe it
makes things easier to understand especially for newbies like me.
The columns must be getting created by implicit means
That was my first impression.
One last question (probably!) on this topic - can the Primary Key be
defined on the "ID" column before adding the DataTable to the DataSet?
If yes, then how?
Thanks once again for your helpful advices.
Regards,
Arpan
Scott M. wrote:
Ok, first of all if you attempt to set your primary key like this:
'Define the Primary Key
Dim dColumn As DataColumn() = {dSet.Tables("U sers").Columns( "ID")}
dSet.Tables("U sers").PrimaryK ey = dColumn
dSet.Tables.Ad d(dTable)
You'll get the object reference error because you are going into the
dataset
and looking for table "Users" before you've added it to the dataset in
the
first place.
As for the creation of the columns without instantiating them (as I
showed
in my last post), I can't explain why it works for you. The columns
must
be
getting created by implicit means. Nonetheless, it is better practice
to
explicitly create the columns ahead of time :
'Create an empty DataSet
Dim dSet As New DataSet
'Create a new table & add columns
Dim dTable As New DataTable("User s")
Dim idCol As New DataColumn("ID" , Type.GetType("S ystem.Int32"))
Dim fNameCol As New DataColumn("Fir st Name",
Type.GetType(" System.String") )
Dim lNameCol As New DataColumn("Las t Name",
Type.GetType(" System.String") )
dTable.Columns .Add(idCol)
dTable.Columns .Add(fNameCol)
dTable.Columns .Add(lNameCol)
dSet.Tables.Ad d(dTable)
'Define the Primary Key
Dim dColumn As DataColumn() = {dSet.Tables("U sers").Columns( "ID")}
dSet.Tables("U sers").PrimaryK ey = dColumn
"Arpan" <ar******@hotma il.comwrote in message
news:11******* *************** @75g2000cwc.goo glegroups.com.. .
Scott, you mean to say that the following lines
dTable.Columns. Add("ID", Type.GetType("S ystem.Int32"))
dTable.Columns. Add("First Name", Type.GetType("S ystem.String"))
dTable.Columns. Add("Last Name", Type.GetType("S ystem.String"))
in reality, DO NOT create the columns "ID, "First Name" & "Last
Name"
in the DataTable in the first place? But if that's the case, I
haven't
used "New DataColumn" anywhere in the code I have cited in post #1
but
the DataGrid does display all the columns & the rows correctly when
the
code is executed. How come?
Moreover, if the above 3 lines do not create any columns, when do
they
get created in the code shown in post #1? In other words, which line
in
the code in post #1 actually creates the 3 columns?
Finally, even if I replace the above 3 lines with the 3 lines you
have
shown & set the Primary Key on the column "ID" before adding the
DataTable to the DataSet, then still the "Object reference not set
to
an instance of an object" gets thrown. Why?
Thanks,
Regards,
Arpan
Scott M. wrote:
These are the culprits:
dTable.Columns. Add("ID", Type.GetType("S ystem.Int32"))
dTable.Columns. Add("First Name",
Type.GetType(" System.String") )
dTable.Columns. Add("Last Name",
Type.GetType(" System.String") )
You don't have any actual DataColumns in existence yet, so how can
you
add
what you don't have to the Columns collection of dTable?
Should be:
dTable.Columns. Add(New DataColumn("ID" ,
Type.GetType(" System.Int32")) )
dTable.Columns. Add(New DataColumn("Fir st Name",
Type.GetType(" System.String") ))
dTable.Columns. Add(New DataColumn("Las t Name",
Type.GetType(" System.String") ))
"Arpan" <ar******@hotma il.comwrote in message
news:11******* *************** @p79g2000cwp.go oglegroups.com. ..
Consider the following code that adds a table to a DataSet
dynamically:
<script runat="server">
Sub Page_Load(ByVal obj As Object, ByVal ea As EventArgs)
'Create an empty DataSet
Dim dSet As New DataSet
'Create a new table & add columns
Dim dTable As New DataTable("User s")
dTable.Columns. Add("ID", Type.GetType("S ystem.Int32"))
dTable.Columns. Add("First Name",
Type.GetType("S ystem.String"))
dTable.Columns. Add("Last Name",
Type.GetType("S ystem.String"))
dSet.Tables.Add (dTable)
'Define the Primary Key
Dim dColumn() As DataColumn =
{dSet.Tables("U sers").Columns( "ID")}
dSet.Tables("Us ers").PrimaryKe y = dColumn
End Sub
</script>
The above code works fine but if the column named "ID" is set as
the
Primary Key before adding the DataTable to the DataSet i.e. if
the 2
lines preceding the "End Sub" line are cut & pasted just above
the
line
"dSet.Tables.Ad d(dTable)", then the following error gets
generated:
Object reference not set to an instance of an object.
pointing to the line
Dim dColumn() As DataColumn =
{dSet.Tables("U sers").Columns( "ID")}
Which "object" is the above error message referring to? Is it the
DataSet or the DataTable or some other object? Also is the error
generating because I am defining the column "ID" as the Primary
Key
before adding the DataTable to the DataSet? If yes, then why
should
this cause the error? After all, I am defining the Primary Key
after
creating the DataTable i.e. the schema of the DataTable is ready
after
which only I am defining the Primary Key, isn't it? So why the
error?
Thanks,
Arpan
Thank you very very very much, Scott, for all the guidance you have
bestowed on me.
Regards,
Arpan
Scott M. wrote:
Also, there is no rule that says that a DataTable *must* be added to a
DataSet at all, so setting the primary key must be possible before adding
the table to the DataSet, since you may not even want to use a dataset
anyway.
"Arpan" <ar******@hotma il.comwrote in message
news:11******** **************@ b28g2000cwb.goo glegroups.com.. .
Yes, the primary key can be set before the table is added to the dataset
How?
Arpan
Scott M. wrote:
Yes, the primary key can be set before the table is added to the dataset.
"Arpan" <ar******@hotma il.comwrote in message
news:11******** **************@ m73g2000cwd.goo glegroups.com.. .
Thanks, Scott, for the suggestions. You have indeed made it easier for
me to grasp this topic & the reason behind the error message. Moreover,
I have always preferred coding in the manner you have shown & not club
2 lines into one which can be very well done in ASP.NET. I believe it
makes things easier to understand especially for newbies like me.
The columns must be getting created by implicit means
That was my first impression.
One last question (probably!) on this topic - can the Primary Key be
defined on the "ID" column before adding the DataTable to the DataSet?
If yes, then how?
Thanks once again for your helpful advices.
Regards,
Arpan
Scott M. wrote:
Ok, first of all if you attempt to set your primary key like this:
'Define the Primary Key
Dim dColumn As DataColumn() = {dSet.Tables("U sers").Columns( "ID")}
dSet.Tables("Us ers").PrimaryKe y = dColumn
dSet.Tables.Add (dTable)
You'll get the object reference error because you are going into the
dataset
and looking for table "Users" before you've added it to the dataset in
the
first place.
As for the creation of the columns without instantiating them (as I
showed
in my last post), I can't explain why it works for you. The columns
must
be
getting created by implicit means. Nonetheless, it is better practice
to
explicitly create the columns ahead of time :
'Create an empty DataSet
Dim dSet As New DataSet
'Create a new table & add columns
Dim dTable As New DataTable("User s")
Dim idCol As New DataColumn("ID" , Type.GetType("S ystem.Int32"))
Dim fNameCol As New DataColumn("Fir st Name",
Type.GetType("S ystem.String"))
Dim lNameCol As New DataColumn("Las t Name",
Type.GetType("S ystem.String"))
dTable.Columns. Add(idCol)
dTable.Columns. Add(fNameCol)
dTable.Columns. Add(lNameCol)
dSet.Tables.Add (dTable)
'Define the Primary Key
Dim dColumn As DataColumn() = {dSet.Tables("U sers").Columns( "ID")}
dSet.Tables("Us ers").PrimaryKe y = dColumn
"Arpan" <ar******@hotma il.comwrote in message
news:11******** **************@ 75g2000cwc.goog legroups.com...
Scott, you mean to say that the following lines
dTable.Columns. Add("ID", Type.GetType("S ystem.Int32"))
dTable.Columns. Add("First Name", Type.GetType("S ystem.String"))
dTable.Columns. Add("Last Name", Type.GetType("S ystem.String"))
in reality, DO NOT create the columns "ID, "First Name" & "Last
Name"
in the DataTable in the first place? But if that's the case, I
haven't
used "New DataColumn" anywhere in the code I have cited in post #1
but
the DataGrid does display all the columns & the rows correctly when
the
code is executed. How come?
Moreover, if the above 3 lines do not create any columns, when do
they
get created in the code shown in post #1? In other words, which line
in
the code in post #1 actually creates the 3 columns?
Finally, even if I replace the above 3 lines with the 3 lines you
have
shown & set the Primary Key on the column "ID" before adding the
DataTable to the DataSet, then still the "Object reference not set
to
an instance of an object" gets thrown. Why?
Thanks,
Regards,
Arpan
Scott M. wrote:
These are the culprits:
dTable.Columns. Add("ID", Type.GetType("S ystem.Int32"))
dTable.Columns. Add("First Name",
Type.GetType("S ystem.String"))
dTable.Columns. Add("Last Name",
Type.GetType("S ystem.String"))
You don't have any actual DataColumns in existence yet, so how can
you
add
what you don't have to the Columns collection of dTable?
Should be:
dTable.Columns. Add(New DataColumn("ID" ,
Type.GetType("S ystem.Int32")))
dTable.Columns. Add(New DataColumn("Fir st Name",
Type.GetType("S ystem.String")) )
dTable.Columns. Add(New DataColumn("Las t Name",
Type.GetType("S ystem.String")) )
"Arpan" <ar******@hotma il.comwrote in message
news:11******** **************@ p79g2000cwp.goo glegroups.com.. .
Consider the following code that adds a table to a DataSet
dynamically:
<script runat="server">
Sub Page_Load(ByVal obj As Object, ByVal ea As EventArgs)
'Create an empty DataSet
Dim dSet As New DataSet
'Create a new table & add columns
Dim dTable As New DataTable("User s")
dTable.Columns. Add("ID", Type.GetType("S ystem.Int32"))
dTable.Columns. Add("First Name",
Type.GetType("S ystem.String"))
dTable.Columns. Add("Last Name",
Type.GetType("S ystem.String"))
dSet.Tables.Add (dTable)
'Define the Primary Key
Dim dColumn() As DataColumn =
{dSet.Tables("U sers").Columns( "ID")}
dSet.Tables("Us ers").PrimaryKe y = dColumn
End Sub
</script>
The above code works fine but if the column named "ID" is set as
the
Primary Key before adding the DataTable to the DataSet i.e. if
the 2
lines preceding the "End Sub" line are cut & pasted just above
the
line
"dSet.Tables.Ad d(dTable)", then the following error gets
generated:
Object reference not set to an instance of an object.
pointing to the line
Dim dColumn() As DataColumn =
{dSet.Tables("U sers").Columns( "ID")}
Which "object" is the above error message referring to? Is it the
DataSet or the DataTable or some other object? Also is the error
generating because I am defining the column "ID" as the Primary
Key
before adding the DataTable to the DataSet? If yes, then why
should
this cause the error? After all, I am defining the Primary Key
after
creating the DataTable i.e. the schema of the DataTable is ready
after
which only I am defining the Primary Key, isn't it? So why the
error?
Thanks,
Arpan
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics | |
by: Daniel |
last post by:
Hello =)
I have an object which contains a method that should execute every x ms. I
can use setInterval inside the object construct like this -
self.setInterval('ObjectName.methodName()', this.pinginterval);
- but is there no way to do this without using the literal ObjectName? If I
write 'this.methodName()' I get "Line 1 Char 1: Object doesn't support this
property or method." in IE, and nothing happens in Firebird.
|
by: Martin |
last post by:
I'd like to be able to get the name of an object instance from within
a call to a method of that same object. Is this at all possible?
The example below works by passing in the name of the object instance
(in this case 'myDog'). Of course it would be better if I could
somehow know from within write() that the name of the object instance
was 'myDog' without having to pass it as a parameter.
////////////////////////////////
function...
|
by: Carlos Lozano |
last post by:
Hi,
What is the right way to create an OCX COM component. The component is
already registerred, but can't create an instance. I am using the reference
to the interop module created.
If I use javascript or vbscript it works.
I will appreciate any help.
I do the following (C#):
|
by: Adam |
last post by:
We have a web site that uses .vb for the web pages and .cs for a class
module. We are getting the error in .NET 2.0 and VS 2005 beta 2. It does
work with .NET 1.1.
When trying to access a page that needs the class module I get an error on
web site:
Object reference not set to an instance of an object
Here is where the error is:
|
by: Luke Matuszewski |
last post by:
Here are some questions that i am interested about and wanted to here
an explanation/discussion:
1. (general) Is the objectness in JavaScript was supported from the
very first version of it (in browsers) ? What about the new syntax of
creating a object using { 'propName1':'propValue1',
'propName2':'propValue2', 'propName3':{ /* another object */ } } - from
what version of JScript/JavaScript it was supported (from what browsers
versions) ?...
| | |
by: Andrew Poulos |
last post by:
With the following code I can't understand why this.num keeps
incrementing each time I create a new instance of Foo. For each instance
I'm expecting this.num to alert as 1 but keeps incrementing.
Foo = function(type) {
this.num = 0;
this.type = type
this.trigger();
}
Foo.prototype.trigger = function() {
|
by: Shailen Sukul |
last post by:
Observed a weird behaviour with object references.
See code listing below:
using System;
using System.Collections.Generic;
using System.Text;
namespace PointerExceptionTest
{
/*
|
by: Philipp Reif |
last post by:
Hi all,
I've got a little hole in my head concerning references. Here's what
I'm trying to do: I'm calling a function, passing the reference of a
business object for editing. The function clones the object, calls an
editor dialog to let the user edit the object, and then - depending on
the DialogResult - assigns either the clone/backup copy or the modified
object itself to the reference. Maybe I'm thinking too much in pointer
references...
|
by: User1014 |
last post by:
A global variable is really just a property of the "Global Object", so
what does that make a function defined in the global context? A method
of the Global Object?
http://developer.mozilla.org/en/docs/Core_JavaScript_1.5_Guide:Defining_Functions
doesn't actually give any insight.
|
by: Ralph |
last post by:
Hi
I don't understand why it's not working:
function schedule(imTop){
this.tdImagesTop = imTop;
}
schedule.prototype.selectEl = function() {
alert(this.tdImagesTop);
|
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, people are often confused as to whether an ONU can Work As a Router. In this blog post, we’ll explore What is ONU, What Is Router, ONU & Router’s main usage, and What is the difference between ONU and Router. Let’s take a closer look !
Part I. Meaning of...
| | |
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 protocol has its own unique characteristics and advantages, but as a user who is planning to build a smart home system, I am a bit confused by the choice of these technologies. I'm particularly interested in Zigbee because I've heard it does some...
|
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 project—planning, coding, testing, and deployment—without human intervention. Imagine an AI that can take a project description, break it down, write the code, debug it, and then launch it, all on its own....
Now, this would greatly impact the work of software developers. The idea...
|
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 presenter, Adolph Dupré who will be discussing some powerful techniques for using class modules.
He will explain when you may want to use classes instead of User Defined Types (UDT). For example, to manage the data in unbound forms.
Adolph will...
|
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 last exercise I practiced was to create a LAN-to-LAN VPN between two Pfsense firewalls, by using IPSEC protocols.
I succeeded, with both firewalls in the same network. But I'm wondering if it's possible to do the same thing, with 2 Pfsense firewalls...
|
by: adsilva |
last post by:
A Windows Forms form does not have the event Unload, like VB6. What one acts like?
|
by: 6302768590 |
last post by:
Hai team
i want code for transfer the data from one system to another through IP address by using C# our system has to for every 5mins then we have to update the data what the data is updated we have to send another system
| | |
by: muto222 |
last post by:
How can i add a mobile payment intergratation into php mysql website.
|
by: bsmnconsultancy |
last post by:
In today's digital era, a well-designed website is crucial for businesses looking to succeed. Whether you're a small business owner or a large corporation in Toronto, having a strong online presence can significantly impact your brand's success. BSMN Consultancy, a leader in Website Development in Toronto offers valuable insights into creating effective websites that not only look great but also perform exceptionally well. In this comprehensive...
| |
