Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Datagrids
- Thread starter sthmpsn1
- Start date
I could be mistaken what you are asking. What you want your datagrid to do is something like this:
database table
---------------------------------------------
ColumnName1 - ColumnName2 - ... - ColumnNamen
entry1 - entry2 - ... - entryn
datagrid
------------------
ColumnName1 entry1
ColumnName2 entry2
... ...
ColumnNamen entryn
Is this what you want?
database table
---------------------------------------------
ColumnName1 - ColumnName2 - ... - ColumnNamen
entry1 - entry2 - ... - entryn
datagrid
------------------
ColumnName1 entry1
ColumnName2 entry2
... ...
ColumnNamen entryn
Is this what you want?
Hmmm...there might be a cleaner way, but off the top of my head here's how I would tackle it:
1. Return the datatable holding the row of information
We'll call this one dtData
2. Create a new datatable object, adding one column to it
(call it whatever you'd like). We'll call this dtEmpty
3. For each field in dtData, I would take that value and
assign it to a new datarow's item(0) value, which I would
then add to the dtEmpty data table.
4. Once I had all the items in teh dtEmpty datatable, I
would bind my datagrid to dtEmpty.
Voila! In theory, you'd have a vertical datagrid view of the
record.
Jack
1. Return the datatable holding the row of information
We'll call this one dtData
2. Create a new datatable object, adding one column to it
(call it whatever you'd like). We'll call this dtEmpty
3. For each field in dtData, I would take that value and
assign it to a new datarow's item(0) value, which I would
then add to the dtEmpty data table.
4. Once I had all the items in teh dtEmpty datatable, I
would bind my datagrid to dtEmpty.
Voila! In theory, you'd have a vertical datagrid view of the
record.
Jack
![[bravo]](/data/assets/smilies/bravo.gif "[bravo] [bravo]")
- Thread starter
- #5
If Datalist (hardly worked with them) can do it, then go for it.
Worst case, you could do the datagrid way.
Um, just a third thought too though:
If you want the users to be able to edit it, why not just create a user interface out of textboxes instead of using a datagrid? You coudl create an object that holds the record values, and just drop the values into the textboxes.
Just a thought anyway
Jack
Worst case, you could do the datagrid way.
Um, just a third thought too though:
If you want the users to be able to edit it, why not just create a user interface out of textboxes instead of using a datagrid? You coudl create an object that holds the record values, and just drop the values into the textboxes.
Just a thought anyway
Jack
- Thread starter
- #7
I think that is a great idea, but the reason I was thinking of using a datagrid was because I wanted to display the user there current information and then have an edit command incase they wanted to change something. So everything could be on one page
could still be on one page.
Textboxes have a ReadOnly property.
When the data is displayed, you could have the textboxes to be in ReadOnly mode. When they click edit, it unlocks all the fields so they can edit them.
1 page, no datagrid crap to worry about.
Jack
Textboxes have a ReadOnly property.
When the data is displayed, you could have the textboxes to be in ReadOnly mode. When they click edit, it unlocks all the fields so they can edit them.
1 page, no datagrid crap to worry about.
Jack
- Thread starter
- #9
yup, pretty much.
If you wanted to get super fancy, you could even change the look of the textbox between viewing and editing (so like the textbox would look like a label or soemting for viewing, but when you click edit it would look more like a text box).
There's alot of stuff you can do with the interface, but yeah, thats how you'd set the read only
jack
If you wanted to get super fancy, you could even change the look of the textbox between viewing and editing (so like the textbox would look like a label or soemting for viewing, but when you click edit it would look more like a text box).
There's alot of stuff you can do with the interface, but yeah, thats how you'd set the read only
jack
- Thread starter
- #11
I do like your example of
1. Return the datatable holding the row of information
We'll call this one dtData
2. Create a new datatable object, adding one column to it
(call it whatever you'd like). We'll call this dtEmpty
3. For each field in dtData, I would take that value and
assign it to a new datarow's item(0) value, which I would
then add to the dtEmpty data table.
4. Once I had all the items in teh dtEmpty datatable, I
would bind my datagrid to dtEmpty.
Do you not recommend doing this?
1. Return the datatable holding the row of information
We'll call this one dtData
2. Create a new datatable object, adding one column to it
(call it whatever you'd like). We'll call this dtEmpty
3. For each field in dtData, I would take that value and
assign it to a new datarow's item(0) value, which I would
then add to the dtEmpty data table.
4. Once I had all the items in teh dtEmpty datatable, I
would bind my datagrid to dtEmpty.
Do you not recommend doing this?
- Thread starter
- #12
Truthfully, I'd to teh textbox thing if it was only ever going to be for one record at a time.
And yeah, you could look at doing it through the CSS. problem is that CSS is mainly look-wise stuff, whereas items like the textbox's ReadOnly property can't be accessed that way (to my knowledge anyway), in which case you'd need code behind.
All of our edit screens in our webapplication use the textbox version, and not direct editing within datagrids.
Jack
And yeah, you could look at doing it through the CSS. problem is that CSS is mainly look-wise stuff, whereas items like the textbox's ReadOnly property can't be accessed that way (to my knowledge anyway), in which case you'd need code behind.
All of our edit screens in our webapplication use the textbox version, and not direct editing within datagrids.
Jack
- Thread starter
- #14
Truthfully, I'd to teh textbox thing if it was only ever going to be for one record at a time.
And yeah, you could look at doing it through the CSS. problem is that CSS is mainly look-wise stuff, whereas items like the textbox's ReadOnly property can't be accessed that way (to my knowledge anyway), in which case you'd need code behind.
All of our edit screens in our webapplication use the textbox version, and not direct editing within datagrids.
Jack
And yeah, you could look at doing it through the CSS. problem is that CSS is mainly look-wise stuff, whereas items like the textbox's ReadOnly property can't be accessed that way (to my knowledge anyway), in which case you'd need code behind.
All of our edit screens in our webapplication use the textbox version, and not direct editing within datagrids.
Jack
sorry, didn't mean to post that twice.
K, Textboxes have a slew of properties that you can change. For instance:
With TextBox1
.BorderStyle = Solid
.BorderWidth = 1
End With
Will give you a text box that has a solid border, and doesn't have the traditional ridged/grooved (always get those mixed up) border.
If you set
With TextBox1
.BorderStyle = NotSet
.BorderWidth = Nothing
End Width
Then that gives you back the regular text box.
Jack
K, Textboxes have a slew of properties that you can change. For instance:
With TextBox1
.BorderStyle = Solid
.BorderWidth = 1
End With
Will give you a text box that has a solid border, and doesn't have the traditional ridged/grooved (always get those mixed up) border.
If you set
With TextBox1
.BorderStyle = NotSet
.BorderWidth = Nothing
End Width
Then that gives you back the regular text box.
Jack
- Status
Similar threads
- Locked
- Question
- Locked
- Question