[thelist] .NET and MSSQL data validation

Joel D Canfield joel at streamliine.com
Thu Jun 28 14:34:27 CDT 2007

I'm working on an intranet project for a friend who is the director of
IT at his company, and generally a sharp guy. we started the project in
classic ASP because that's what I know. he's taking a class in .NET
right now. he thinks .NET is a better platform for this tool but wants
to get a quick and dirty update tool built in classic ASP, then have his
summer interns input data while I get up to speed on .NET and continue
the project. fully aware of Alexander Pope's cautionary tale [1] we each
have a question:

His question: aware of .NET's data validation capabilities, he wonders
of it can also enforce restraints created in the database (for instance,
this office has these data ports, so if that office is chosen, only
allow choices of data ports that really exist in the office.) I would
normally use a combination of scripting and db logic to enforce that.
there's no point in building that logic in the quick and dirty, if .NET
is just going to supplant it. if it doesn't do that (which is my guess)
then we build the db logic with the classic ASP quick and dirty, because
we'll be reusing it almost verbatim in the .NET version.

My question: how long does it take to get from pretty comfortable with
classic VBScript ASP and MSSQL and object-oriented life in general, but
with zero real programming languages, to a point where I can build this
tool in .NET without using the WYSIWYG designer thingies I've seen?

thanks ever so much


[1] http://www.bartleby.com/100/230.99.html

More information about the thelist mailing list