Thank you everyone for being so excited with us. We are so excited and cant wait to see this beautiful baby come out of her beautiful mother!

I am so in love with April and love this baby so much, and I have not had a time to hold her yet. 

We just did the ultrasound photos yesterday and its amazing to see how much this baby has developed in just 20 weeks.   Its amazing to think that April is going to nearly double in size for this baby.  She is 20 weeks along, and we have 4 more months.

Here are a couple of photos:

Click Here for more pictures and higher res photos

Baby Feet:

I decided to throw up some code that I like to use, but hate re-writting.  This is how I do some of the dynamic SQL statements.  If you think there is a better way of doing it, please let me know.  This has worked very well for me so far.

USE GO /****** Object: StoredProcedure [dbo].[RS_Reservations_Get_List_By_DateRange] Script Date: 09/08/2007 17:14:28 ******/ SET ANSI_NULLS ON GO SET QUOTED_IDENTIFIER ON GO ------------------------------------------------------------------------------------------------------------------------ -- Date Created: Tuesday, November 18, 2006 -- Created By: Travis ------------------------------------------------------------------------------------------------------------------------ CREATE PROCEDURE [dbo].[RS_Reservations_Get_List_By_DateRange] @StartDate datetime, @EndDate datetime, @CompanyID uniqueidentifier, @LocationID uniqueidentifier, @ReservationObjectID uniqueidentifier AS Declare @BaseSQL nvarchar(900) Declare @WhereSQL nvarchar(900) Declare @FinalSQl nvarchar(900) set @BaseSQL = ' SELECT [ReservationID], [FK_ReserveObjectID], [UTC_ReservationDateTime], [ReservedMinutes], [HoldExpires], [Canceled], [UTC_Created], [UTC_Updated], [FK_CreatedBy], [FK_CanceledBy], [FK_SalesOrderItemID] FROM [dbo].[viewReservationAssociations] ' /* Set the initial value */ set @WhereSQL = '' /* Build the rest of the where clause dynamicly */ if @StartDate IS NOT NULL AND @EndDate IS NOT NULL begin if @WhereSQL = '' begin set @WhereSQL = ' WHERE ' end else begin set @WhereSQL = @WhereSQL + ' AND ' end set @WhereSQL = @WhereSQL + ' [UTC_ReservationDateTime] between ''' + Convert(varchar(20), @StartDate) + ''' AND ''' + Convert(varchar(20), @EndDate) + '''' end if @CompanyID IS NOT NULL begin if @WhereSQL = '' begin set @WhereSQL = ' WHERE ' end else begin set @WhereSQL = @WhereSQL + ' AND ' end set @WhereSQL = @WhereSQL + ' [CompanyID] = ''' + Convert(varchar(40), @CompanyID) + '''' end if @LocationID IS NOT NULL begin if @WhereSQL = '' begin set @WhereSQL = ' WHERE ' end else begin set @WhereSQL = @WhereSQL + ' AND ' end set @WhereSQL = @WhereSQL + ' [LocationID] = ''' + Convert(varchar(40), @LocationID) + '''' end if @ReservationObjectID IS NOT NULL begin if @WhereSQL = '' begin set @WhereSQL = ' WHERE ' end else begin set @WhereSQL = @WhereSQL + ' AND ' end set @WhereSQL = @WhereSQL + ' [ReserveObjectID] = ''' + Convert(varchar(40), @ReservationObjectID) + '''' end /* Create the final SQL string */ set @FinalSQL = @BaseSQL + @WhereSQL + ' ORDER BY [UTC_ReservationDateTime] DESC ' /* Execute the SQL */ EXEC dbo.sp_executeSQL @statement = @FinalSQL

I have been involved with web design for many years.  Even with 15 years under my belt, I still am amazed when I find something I didn't know. I am not saying I know everything, its just those things that you wish you knew about years and years ago that really get your excitement up.

The other day, I was looking at the HackerSafe code that my company (http://www.amhosting.com) has on its website.  I saw the way they put in an image tag and I was like, "what the heck.. they have a bug in their code".  Before I went crazy, I decided to look at my live production code and noticed that the way they linked the image was the same in their code they were trying to give me.

So you know what I am talking about... this is what they put in the code: 

src="//images.scanalert.com/meter/www.amhosting.com/12.gif"

Notice how src="//  part for it.  That is where the magic happens

This is why its important.  This image is located on my company website: (Secure SSL Mode)

https://www.amhosting.com/MyAccount/UpdateBillingContactInformation/tabid/746/Default.aspx

and the same image code is located on a non https page: (No SSL)

http://www.amhosting.com/Home/tabid/293/Default.aspx

The browser actually knows based on what state your page is on what to call to the remote server.   If you didn't have your code like this, it would throw a security error to the end user asking them if they want to show insecure images. Not only does that break credibility, but it also is very annoying between page clicks. 

I know this is a very "small" finding, but it is very useful when building ecommerce sites that link to outside content. I hope you are as excited as I am with this very small find.