MikeP

We're finding a situation where a dataset is failing, but when we remove a field or two from the select statement, it will work fine. Does anybody know if there is an explicit limit to the number of fields that can be handled by a dataset? This is really odd behavior, and I can't find any documentation that says one way or another. Any ideas?

I've been in a spirited debate with a co-worker over the reusability of stored procedures. The two positions are as follows: He states that all "select" procedures should use "select *" versus selecting specific fields, in order to be able to reuse the stored procedure by other apps. Also, if the table structure changes, you are covered. My position is that I shouldn't have to clog my bandwidth and ram with fields stuff that my app doesn't need. Also, with very rare exceptions, there aren't many situations where the selection criteria is broad enough to be used by more than one application. Plus, pulling all the additional information could result in a performance hit. Both arguments have merit. What say you? :cool:

I'd like to create a databound custom control that I can pass a parameter to in order to filter its dataset. The scenario is as follows: I'd create a generic StudentInfo control that would display Name, Address, and Phone Number from the Student Info table. This generic StudentInfo control would include a dataset using SQL like "Select * from Student Info". The form that contains the StudentInfo control would then pass it an SSN, upon which it would filter the data and only display the info for that particular SSN. Sounds like a simple task, yet I'm having some difficulties. Anybody want to have a go? Cheers!

Try this... Sadly, the multi-column listbox went away with the advent of .NET (odd, because it was really handy). You'll have to concatenate your values into a single element in order to get them to both show up. Try something like this: file_name & vbtab & cstr(size) That will give you something like what you're looking for. As for why Microsoft abandoned one of their best controls...beats me?! Cheers! :D

Works like a champ!!! Thanks a million, Alex!!! Happy holidays, btw. Cheers!

Well, we've got partial success... Alex, Your solution works great with everything except combo boxes, for some strange reason. Once you land on a combo box, we're back to having to hit the "TAB" key to get out of it. Any ideas? Thanks for the reply, btw! Cheers!

I can tab through the fields on my form just fine, but I also want the enter key to do the same thing (move to the next field). This simple little thing wasn't a problem in VB6 but now it seems to be a big hassle to do in .NET. Anyone got a quick fix for this? Cheers!

I've got an application that displays data in a dataset. It works fine, but I'm having trouble capturing the values that are being displayed on the controls. For example, I databind the "text" property of a control to a particular dataset field ("name", for illustration purposes) and it displays the data fine ("smith") at runtime, but if I try and messagebox the current value of the "text" property of that control, I get the original default value (""), instead of the currently displayed value ("smith"). Simply put, how can I capture the value that is currently being displayed in the control, since the "text" property apparently isn't really being modified? I need it so I can use it in a parameter for update and delete functionality. This stuff was so much simpler in VB6!!

I want to use a checkedlistbox control and need it to be populated with rows from a dataset. I've found nothing in books or at MSDN.com to help. Surely I'm not the only one who's wanted to do this. Can anybody help? I can get the checkedlistbox to display one column, but not all of them. Please help!

I'm working on a change approval screen that would work well with a checked listbox, but I can't find any good documentation on how to bind it to a dataset and display the columns from the dataset. Any ideas or examples? Thanks!

That works. Thanks a bunch!!! Cheers!

I may be missing something here, but the VB example doesn't work for me. The subroutine "whatever" doesn't fire.

Is there an easy way in VB.NET for a form to pass a value as an argument to be used by a second form? For example, Form1 has a field "SSN" and Form2 will display info based on the value of SSN in Form1. Of course, I could use a global variable or something like that, but it'd be nice (and pretty elegant, codewise) to be able to just say something like "Form2.show(byval SSN as string)". Perhaps by creating a new type of Form class? Any thoughts? Cheers!