[thelist] .NET and MSSQL data validation

Joel D Canfield joel at streamliine.com
Thu Jun 28 17:25:54 CDT 2007

[reordered to put the most important on top]

> Second, constraints and such should be a DB level function - 
> not a code level issue. Use the DB first, code as a backup / 

yes, right, exactly - I didn't 'splain myself well.

in the db, *this* data port is connected to *that* office; all proper db
constraints in place.

now, the user goes to set up a new user's info in the db. when they
select the office New User is assigned, and then go to assign their
computer to a data port, the select should only populate with data ports
from that office. normally, I'd restrict the select options using code
(okay, probably way back in the SQL query somewhere.)

will .NET see that connection in the SQL db and assume it for me? that
was what I really meant to ask.

> First off, I'm not a big fan of the built in validation that 
> is part of the web controls. I rolled my own. But I tend to 
> be a maverick about such things.

you may be a maverick, but I've always leant thataway myself, so that's
useful info

> And how long will it take you to be comfortable with dotNet? 
> How long did it take you to be comfortable with ASP? I'd say 
> at about half that long with dotNet due to experience helping 
> you out. Your mileage may vary. ;-)

huh. understood. not loved, but understood.

thanks. still open to other input.


More information about the thelist mailing list