View Complete Post
I am a learning-as-I-go person without formal training. I have been working with Access databases for about 10 years, and have begun working with SQL in the last 5 years or so. The system in user here is a 2K3 server (8xXeon 2.8Ghz, 12GB RAM,
1TB HDD) running SQL Server 2005 (32bit). I am trying to develop a SQL query (view) which looks for values of one table' field at specific times based on a table of those times. When I use a datetime variable, that particular value at
that particular datetime will be returned. When I try to replace the variable with the datetime result of a second query(view), no data is returned. The code is below.
SET NOCOUNT ON
DECLARE @StartDate DateTime
DECLARE @EndDate DateTime
SET @StartDate = '2010-09-30 04:59:00' -- Need to replace this value with the the list of 'PriVolCk' datetimes
SET NOCOUNT Localized Datetime formatting using select query The article Localized Datetime formatting using select query was added by pankaj.sharma on Monday, March 14, 2011.IntroductionWhen and how to use sql formatting functions to format datetime values when it is being used by the application that is target to be run on different locale and culture.Problem StatementIf schema of a TimeTable is as follows-Activity StartDate
I'd like to have the date and time from server.
DateTime.Now Is ok?
Must be something else?
I am new to gridview.
I want to make a gridview. Its row when selected should direct me to a specific .aspx page.Each row should direct to a different page.
Should I use querystrings for this? Please suggest.
I'm getting the following error:
[ArgumentOutOfRangeException: Value to add was out of range.
Parameter name: value]
System.DateTime.Add(Double value, Int32 scale) +7657639
System.DateTime.AddDays(Double value) +19
The line from which this error originates has the following code:
expires = Now.AddDays(30)
It occurs irregularly and irreproducably. The server date/time is correct and set to GMT. I've heard that it could be some curiosity to do with timezones, but that is speculative.
It seems that we're some time from the year 10,000 yet, so I can't understand why adding thirty days to the current time could cause this! Any ideas? Culture settings perhaps?
MSDN Magazine October 2003
This month Aaron Skonnard covers how keys work in XSLT, XSLT match and select attributes, SelectNodes order, finding