VB.NET web form to SQL database

[paulyXvpf]

Subject: VB.NET - forms to data - SQL


Hi,

Stuck on a project here. ASP.NET / VB / SQL. Trying to get a VB.NET check box to write a True or False value into a SQL database. Having a bear of a time with this.

See my sample data / database schema here:

http://sql-paul.com/press/default.aspx

I was trying to build some programming with Psuedo Code snips from the net... does this logic make sense?
***********
***********

if chkDayShift is selected
        write to sql table the value 1 (true) 
    where column name = current checkbox's label
else
    write to sql table the value 0 (false) 
    where column name = current checkbox's label
 
***********
 
if chkDayShift is selected
        write to ref2 value 1 
    where dayshift = chkDayShift
else
    write to ref2 value 0
    where dayshift = chkDayShift
 
***********

I saw this snippet from the net... is this something that should be in the command button code?
*******************************
Code to check a CheckBox's state
********************************

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As_
System.EventArgs) Handles Button1.Click
If CheckBox1.Checked = True Then
TextBox1.Text = "Checked"
Else
TextBox1.Text = "UnChecked"
End If
End Sub  

*******************************

Any help would be great... source samples if you can please.
Best,
Paul

[tlhintoq]

if chkDayShift is selected

I'm a C# guy, not VB but...

In C# we would be looking at the Checked property, not the Selected property.

if (chkDayShift.Checked) 
{
// blah
// blah
}

[paulyXvpf]

Thanks tlhintoq...

Question 1: Any chance you could copy/paste the entire C# block if you have it handy? :-) C# could still be a useful snip, I could paste into the VB project and let the compiler flag the syntax errors!! At least I'd have a leg up on the project.

Question 2: about your if (chkDayShift.Checked) block.... does the source code get written in the submit button coding itself after the
"Private Sub Button1_Click"???

Sorry if I sound so green, the only VB/C#/SQL I've got are my corny tutorials at http://sql-paul.com. Learning more everyday!!

Thanks buddy,
Later
Paul

[tlhintoq]

Question 1: Any chance you could copy/paste the entire C# block if you have it handy? :-)

I'm not trying to be evasive, I promise. But copy *what* C# block? I don't have a time scheduling program already written. I was just showing you how a checkbox in C# compares the .Checked property as compared to how you were doing "is selected".

Question 2: about your if (chkDayShift.Checked) block.... does the source code get written in the submit button coding itself after the
"Private Sub Button1_Click"???

You could do it that way, though I very rarely write any method directly into the button click handler. It becomes difficult to call later when you need to re-use that same function. Instead I write a method to do what I need it to do, then have the button.click handler call that method.

private void MyCoolButton_click(object sender, eventargs e)
{
     DoCoolFunction();
}
 
private void DoCoolFunction()
{
   // Here is 100 lines of cool code that actually performs a task
}
 
private void DoTotalProcess()
{
     DoMathFunction();
     DoCoolFunction(); // Now I can reuse Cool function more easily
     DoGraphFunction();
}
 

The concept here is to write small descrete methods that have only one purpose in life. They are black boxes that know little or nothing of the world around them. They take in parameters, they return parameters. Then if you need an entire process performed, you call 20 of the descrete functions in the right order. This is much better than writting one giant function that performs 20 steps. What would happen if you had to remove one step, or add one step? In the example above you could comment one method call, or insert a method call, and keep the overall process clean and human readable.

[paulyXvpf]

Hi tlhintoq - thats really helpful... thanks... I'll move my efforts in that direction.

important points I gathered from you:
> thlintoq - checked as opposed to 'is selected'
--- I saw some other code leaning that direction

> thlintoq - avoid writing methods into button click handlers
--- I see your point on this, easier to modify later, etc

> thlintoq - calls to functions
--- I've seen small examples of this, calls are better for reuse especially
during program changes

Thanks buddy,
big help
later
paul