|
Interaction of Web Controls Using Events |
|
|
By host on
11/30/2007 12:50 PM
|
|
|
|
One of the tricky aspects of using web controls in a .NET Web Application is the interaction of web controls. A scenario that may accurately describe the need for such interaction would be a master page that contains one web control that provides a search functionality and another that allows data entry functionality for the item recalled and selected from the search web control.
The use of “Events” works very well. I have used these quite extensively in my past .NET Web Application projects. A quick example of how an Event can be implemented:
Web Control 1 (we’ll call it webControl1) will be the instigator of the event. “DoSomething” will be the name of the event. The Event will need to be declared at the top of the class by using the following syntax:
Public Event DoSomething() ...
|
 |
|
|
More...
|
|
|
INTERSECT Operator |
|
|
By host on
11/26/2007 12:49 AM
|
|
|
|
In my recent research for filtering options I ran across an operator that I had never considered: the INTERSECT operator. This operator was introduced with the release of SQL Server 2005.
The INTERSECT operator returns unique values from where they exist in both queries being evaluated. A sample of how this may appear in a query is as follows:
SELECT ...
|
|
|
|
|
More...
|
|
|
Agile Development |
|
|
By host on
11/18/2007 9:12 PM
|
|
|
|
A fellow developer and I often have discussions regarding the subject of Agile Development. I often am on the critical side of the discussion. Recently, I have been researching this method of development further so that my view point is from what the method is rather than the assumption of what I think it is.
|
|
|
More...
|
|
|
Red-Gate's SQL Dependency Tracker |
|
|
By host on
11/14/2007 9:13 AM
|
|
|
|
Being a visual person, I was looking for a tool that could quickly present my database schema in a graphical format. Qucikly identifying the dependecies that the objects in my database had with eachother was my objective. The benefit of having this information available in such a manner was so that I could state with confidence the effects of modification to any object in the database. Also by having this information, it makes building queries and stored procedures much easier.
I recently installed SQL Dependency Tracker by Red-Gate. This tool is designed to meet my objective. Unlike alot of tools where they pack in so much functionality that the use requires a 300 page manual, this tool was extremely intuitive. Literally within seconds I was able to view the dependencies of my schema.
To obtain my schema, I simply clicked on the "Add Objects To My Project" but ...
|
|
|
|
|
More...
|
|
|
Creating Multi-Segmented Files Using T-SQL (Part 3) |
|
|
By host on
11/11/2007 6:56 PM
|
|
|
|
In part 2 of this blog series, I presented how to prepare a SQL statement that will produce the Header Segment of a multi-segmented fixed length file. As part of that blog entry, I listed items that should be considered when preparing the string that would ultimately be returned when the SQL statement is executed. These considerations should also be part of the building of the remainder of the segments that are involved in this file.
The specific example that is being constructed in this series is a very simple one. It contains 3 segments:
- Header Segment
- Client Segmnet
- Footer Segment
A sample of the content of these segments are as follows:
Header Segment: 01HTV200711040000000000170
Client Segment: 021234567890 &nbs ...
|
|
|
|
|
More...
|
|
|
Creating Multi-Segmented Files Using T-SQL (Part 2) |
|
|
By host on
11/7/2007 10:38 PM
|
|
|
|
In my previous blog entry, I introduced the concept of multi-segmented fixed length files and a brief discussion of the challenges that they face for a developer. In this blog entry I will discuss how such a file can be produced using T-SQL.
In the sample provided in my previous blog entry, we had a fairly simple multi-segment file:
Header Segment: 01HTV200711040000000000170
Client Segment: 021234567890 JOHN DOE 123 MAIN ST…
Footer Segment: 09HTV000000000000300.32
To produce the above noted file, each segment will be created by three separate SQL Statements. I will begin with the Header Segment. In this segment, we have four pieces of da ...
|
|
|
|
|
More...
|
|
|
Creating Multi-Segmented Files Using T-SQL (Part 1) |
|
|
By host on
11/5/2007 2:05 PM
|
|
|
|
There have been many times when I needed to produce a multi-segment fixed length file that is to be processed by another application. What makes a multi-segment file unique is that each segment may not match the previous segment’s layout. For example, a simple multi-segmented file may contain a header segment, a client segment and a footer segment. To illustrate this, below is an example:
Header Segment: 01HTV200711040000000000170
Client Segment: 021234567890 JOHN DOE 123 MAIN ST…
Footer Segment: 09HTV000000000000300.32
At first glance this example may seem like a random collection of numbers and letters; but based upon the defined fie ...
|
|
|
|
|
More...
|
|
|
Error Trapping In SQL Server |
|
|
By host on
11/2/2007 7:25 AM
|
|
|
|
I thought it would be valuable to illustrate the differences in syntax for error trapping in stored procedures using SQL Server 2000 and 2005. I have used both extensively and I found that the syntax that is used in SQL Server 2005 is not only easier to read for troubleshooting purposes but also much more flexible for more complex error handling.
Below is a sample from SQL Server 2000:
BEGIN TRANSACTION
...(SQL Statements Here)
If @@Error <> '0'
BEGIN
&n ...
|
|
|
|
|
More...
|
|
|
Careful Consideration of Deleting |
|
|
By host on
10/25/2007 12:57 PM
|
|
|
|
“To delete, or not to delete: that is the question. Whether ‘tis nobler in the database to accumulate the bits and bytes of outrageous data or to take arms against a sea of auditors and by techie-speak end them?”
Now that I have sufficiently geek-ized Hamlet for my intro; I would like to say a few words regarding the deletion of data. In the design of an application, whether or not to allow data to be deleted from a database through the user interface should be very carefully considered.
Considerations of how the system will be used, how extensively the system is used, value of the data, data relationships and other dependencies are important. It would be unrealistic to say “never delete”; although, it could be argued that deleting should be rarely used.
Carefully listen to those who are defining your development specifications. I have often found that when it is requested to have the ability to delete a r ...
|
|
|
|
|
More...
|
|
|
Eliminating Duplicate Records |
|
|
By host on
10/21/2007 12:12 AM
|
|
|
|
In the magic world of Pleasantville, software executes without a flaw, data is entered into databases clean and without error. DBAs and Developers spend their days playing chess in the park while their applications hum along in the server room. Unfortunately, we do not live in Pleasantville and there are times when data that is entered into databases is duplicated. Regardless of the cause of the duplication, the cleanup can be a challenge.
If you were working with a small set of data, or simply a glutton for mind-numbing work, one could simply scroll through the records deleting every other record thus cleaning up the du ...
|
|
|
|
|
More...
|
|