Support Wikipedia. Please donate

HTC Wildfire S

With the Android rage spreading like wildfire, I decided to buy a smart phone with an Android OS. I owned a Nokia N70 for 4 years and had no issues with it. After thorough search for reviews on Android phones of Samsung, LG and HTC, I purchased the HTC Wildfire S. It is supposedly a low end smart phone (and the only HTC phone I could afford, i did not want to buy the original Wildfire as the resolution is supposedly low).
I am really happy I purchased it. It is a good companion on the move, always keeping me occupied with the music, camera and internet connectivity.
The only minor issues I find with it are:
1. One feature that I loved with my Nokia was that plenty of themes were available, which I would change once every couple of days. This seems impossible on the HTC. Only wallpapers are available. Scenes and skins in HTC have not impressed me
2. The socket for connecting the handsfree seems to be crude, and after I plug the ear plugs in and insert the jack into the socket, I hear a discomforting noise till the jack comfortably sticks inside the socket.
3. The memory is 150 MB, which I feel is a insufficient if the number of apps grows.

Other than that, I feel I have made a wise decision in buying the Wildfire S.

Trip to Yelagiri hills

Yelagiri is a hill station in the Jolarpet district of Tamil Nadu in India. It is about 240 kms from Chennai and about 160 kms from Bangalore. Its not a hill station in the true sense that, the temperature is not below 20 degree Celsius, you dont find yourself surrounded by fog, or do you get to see some breathtaking view points. Its a town on a hill, its altitude is about 1400 metres from sea level.
When we had been there, it was sunny, but due the winds we felt the weather was pleasant.
I had booked accommodation in a hotel, Golden nest, a week in advance. It was a very clean and calm place with a friendly manager in charge of it. You could try it out too in case you plan to visit Yelagiri (http://hotelgoldennestyelagiri.com/).

On the way up the hill, you would have to negotiate 14 hairpin bends (each named after a Tamil poet/poetess).
The popular places to visit would be the Punganur lake, the park (you could skip the musical fountain which happens at 7 PM as the fountains don't dance in sync with the music :) ), Swami malai hills (which is a 2km trek from a place called Mangalam), Lord Murugan temple.
One place which we visited, though it isnt popular is the Andal temple (the access is through a mud road, once you take the right turn close to the Periyar statue).

Overall it was a calm trip away from the noise of the city. It helped us to calm our nerves and refresh ourselves for the hectic week ahead.

Strange error in SSIS for precedence constraint expression

I received a strange error while trying to run a SSIS package in Visual Studio 2008. The error reflected that I had set the precedence constraint incorrectly.

Following is the screenshot of the package that I had created

The parent 'Execute SQL Task' would run a query that would fetch a single integer field from a table in the the database.
select value from tmp_SSISbranch where name= 'condition2'
I had created a variable 'Convalue' in the package by choosing SSIS --> Variables from the menu bar of Visual Studio, for saving the field value.

I had added 3 different precedence constraints - 1 for the failure of the parent task, and 2 constraints for 2 different ranges of values for the integer field. On setting the expressions for the precedence contraints, there was no prompt or warning, but when I tried to execute the package, I was faced with the strange error.

Error at Package: The expression "@Convalue > 10" must evaluate to True or False. Change the expression to evaluate to a Boolean value.
Error at Package: There was an error in the precedence constraint between "Execute SQL Task" and "Data Flow Task".
 (Microsoft.DataTransformationServices.VsIntegration)

I had ensured that the precedence constraints evaluated to a boolean value, so the error puzzled me.

After toiling for hours and looking up for resources on the net went in vain, I realized that the issue must be because of the variable that I had created for saving the result of the query executed by the parent task.

I had created the package variable with the scope of the parent task rather than creating it as a package variable. Once I deleted and recreated the variable with the scope as 'package', the execution ran fine.

So, ensure that the variable is of the correct scope.