Hi All,
When I use the "between" statement
in the query analyzer in MRS, it will not poplulate the data fields.
when I remove the between statement, it runs fine. The parameters in
the
between statement are correct, and I tried different paramenters such
as
a date between 2002 and 2007, which I know is in the db same problem.
I have service packed SQL and VizStudio no help.
Thanks,
>Scott
here's a snippette:
No results using this.
Where Year >= 2006
And Month BETWEEN @.BEGINDATE AND @.ENDDATE
Group by etc......you need to convert your begin and enddate parameters to Months for this to
work, you can use MONTH(@.BeginDate) to do this.
"scott" <dunnscott@.gmail.com> wrote in message
news:1185297699.337926.89340@.57g2000hsv.googlegroups.com...
> Hi All,
> When I use the "between" statement
> in the query analyzer in MRS, it will not poplulate the data fields.
> when I remove the between statement, it runs fine. The parameters in
> the
> between statement are correct, and I tried different paramenters such
> as
> a date between 2002 and 2007, which I know is in the db same problem.
> I have service packed SQL and VizStudio no help.
> Thanks,
>>Scott
> here's a snippette:
> No results using this.
> Where Year >= 2006
> And Month BETWEEN @.BEGINDATE AND @.ENDDATE
> Group by etc......
>
Showing posts with label goofy. Show all posts
Showing posts with label goofy. Show all posts
Monday, March 19, 2012
Goofy Bullsh!t SQL Server 2005 Date Values
What's with this software? Every day its a new surprise with some goofy
bullsh!t.
I finally make time to try to finish building out ASP.NET 2.0 Membership
logging and reporting code and today its user data in the SQL Server 2005
aspnet_Membership table such as LastLockoutDate and FailedPassword with date
values for all users entered as 1/1/1754.
Not only is this goofy bullsh!t it is grossly incorrect goofy bullsh!t. I
have used one of my three test users to test getting locked out so I could
learn to use the Unlock method and I certainly did not enter that user's
incorrect credentials on 1/1/1754. I have no idea how the other users have
data has been manipulated either.
What the heck is going on here?
<%= Clinton Gallagher
NET csgallagher AT metromilwaukee.com
URL http://www.metromilwaukee.com/clintongallagher/If a Goofy programmer read the goofy doc before posting goofy messages, he
would fined that 1/1/1754 for the lockout data means it has not been locked
out.
http://msdn2.microsoft.com/en-us/library/system.web.security.activedirectorymembershipprovider.aspx
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"clintonG" <csgallagher@.REMOVETHISTEXTmetromilwaukee.com> wrote in message
news:%230DLIENiGHA.1264@.TK2MSFTNGP05.phx.gbl...
> What's with this software? Every day its a new surprise with some goofy
> bullsh!t.
> I finally make time to try to finish building out ASP.NET 2.0 Membership
> logging and reporting code and today its user data in the SQL Server 2005
> aspnet_Membership table such as LastLockoutDate and FailedPassword with
> date values for all users entered as 1/1/1754.
> Not only is this goofy bullsh!t it is grossly incorrect goofy bullsh!t. I
> have used one of my three test users to test getting locked out so I could
> learn to use the Unlock method and I certainly did not enter that user's
> incorrect credentials on 1/1/1754. I have no idea how the other users have
> data has been manipulated either.
> What the heck is going on here?
> <%= Clinton Gallagher
> NET csgallagher AT metromilwaukee.com
> URL http://www.metromilwaukee.com/clintongallagher/
>|||DOH!!!
Sorry, couldn't resist...|||I don't use the AD Provider but I do see by the document you refer to that
the explanation of this goofy date sh!t is much more lucid and complete than
in other documents I did and have read [1] but still happen to have missed
the pithy sentence that is supposed to pass for documentation.
<%= Clinton Gallagher
NET csgallagher AT metromilwaukee.com
URL http://www.metromilwaukee.com/clintongallagher/
[1]
http://msdn2.microsoft.com/en-us/library/system.web.security.membershipuser.lastlockoutdate.aspx
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:etI$pGOiGHA.4512@.TK2MSFTNGP02.phx.gbl...
> If a Goofy programmer read the goofy doc before posting goofy messages, he
> would fined that 1/1/1754 for the lockout data means it has not been
> locked out.
> http://msdn2.microsoft.com/en-us/library/system.web.security.activedirectorymembershipprovider.aspx
>
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "clintonG" <csgallagher@.REMOVETHISTEXTmetromilwaukee.com> wrote in message
> news:%230DLIENiGHA.1264@.TK2MSFTNGP05.phx.gbl...
>> What's with this software? Every day its a new surprise with some goofy
>> bullsh!t.
>> I finally make time to try to finish building out ASP.NET 2.0 Membership
>> logging and reporting code and today its user data in the SQL Server 2005
>> aspnet_Membership table such as LastLockoutDate and FailedPassword with
>> date values for all users entered as 1/1/1754.
>> Not only is this goofy bullsh!t it is grossly incorrect goofy bullsh!t.
>> I have used one of my three test users to test getting locked out so I
>> could learn to use the Unlock method and I certainly did not enter that
>> user's incorrect credentials on 1/1/1754. I have no idea how the other
>> users have data has been manipulated either.
>> What the heck is going on here?
>> <%= Clinton Gallagher
>> NET csgallagher AT metromilwaukee.com
>> URL http://www.metromilwaukee.com/clintongallagher/
>
bullsh!t.
I finally make time to try to finish building out ASP.NET 2.0 Membership
logging and reporting code and today its user data in the SQL Server 2005
aspnet_Membership table such as LastLockoutDate and FailedPassword with date
values for all users entered as 1/1/1754.
Not only is this goofy bullsh!t it is grossly incorrect goofy bullsh!t. I
have used one of my three test users to test getting locked out so I could
learn to use the Unlock method and I certainly did not enter that user's
incorrect credentials on 1/1/1754. I have no idea how the other users have
data has been manipulated either.
What the heck is going on here?
<%= Clinton Gallagher
NET csgallagher AT metromilwaukee.com
URL http://www.metromilwaukee.com/clintongallagher/If a Goofy programmer read the goofy doc before posting goofy messages, he
would fined that 1/1/1754 for the lockout data means it has not been locked
out.
http://msdn2.microsoft.com/en-us/library/system.web.security.activedirectorymembershipprovider.aspx
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"clintonG" <csgallagher@.REMOVETHISTEXTmetromilwaukee.com> wrote in message
news:%230DLIENiGHA.1264@.TK2MSFTNGP05.phx.gbl...
> What's with this software? Every day its a new surprise with some goofy
> bullsh!t.
> I finally make time to try to finish building out ASP.NET 2.0 Membership
> logging and reporting code and today its user data in the SQL Server 2005
> aspnet_Membership table such as LastLockoutDate and FailedPassword with
> date values for all users entered as 1/1/1754.
> Not only is this goofy bullsh!t it is grossly incorrect goofy bullsh!t. I
> have used one of my three test users to test getting locked out so I could
> learn to use the Unlock method and I certainly did not enter that user's
> incorrect credentials on 1/1/1754. I have no idea how the other users have
> data has been manipulated either.
> What the heck is going on here?
> <%= Clinton Gallagher
> NET csgallagher AT metromilwaukee.com
> URL http://www.metromilwaukee.com/clintongallagher/
>|||DOH!!!
Sorry, couldn't resist...|||I don't use the AD Provider but I do see by the document you refer to that
the explanation of this goofy date sh!t is much more lucid and complete than
in other documents I did and have read [1] but still happen to have missed
the pithy sentence that is supposed to pass for documentation.
<%= Clinton Gallagher
NET csgallagher AT metromilwaukee.com
URL http://www.metromilwaukee.com/clintongallagher/
[1]
http://msdn2.microsoft.com/en-us/library/system.web.security.membershipuser.lastlockoutdate.aspx
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:etI$pGOiGHA.4512@.TK2MSFTNGP02.phx.gbl...
> If a Goofy programmer read the goofy doc before posting goofy messages, he
> would fined that 1/1/1754 for the lockout data means it has not been
> locked out.
> http://msdn2.microsoft.com/en-us/library/system.web.security.activedirectorymembershipprovider.aspx
>
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "clintonG" <csgallagher@.REMOVETHISTEXTmetromilwaukee.com> wrote in message
> news:%230DLIENiGHA.1264@.TK2MSFTNGP05.phx.gbl...
>> What's with this software? Every day its a new surprise with some goofy
>> bullsh!t.
>> I finally make time to try to finish building out ASP.NET 2.0 Membership
>> logging and reporting code and today its user data in the SQL Server 2005
>> aspnet_Membership table such as LastLockoutDate and FailedPassword with
>> date values for all users entered as 1/1/1754.
>> Not only is this goofy bullsh!t it is grossly incorrect goofy bullsh!t.
>> I have used one of my three test users to test getting locked out so I
>> could learn to use the Unlock method and I certainly did not enter that
>> user's incorrect credentials on 1/1/1754. I have no idea how the other
>> users have data has been manipulated either.
>> What the heck is going on here?
>> <%= Clinton Gallagher
>> NET csgallagher AT metromilwaukee.com
>> URL http://www.metromilwaukee.com/clintongallagher/
>
Goofy Bullsh!t SQL Server 2005 Date Values
What's with this software? Every day its a new surprise with some goofy
bullsh!t.
I finally make time to try to finish building out ASP.NET 2.0 Membership
logging and reporting code and today its user data in the SQL Server 2005
aspnet_Membership table such as LastLockoutDate and FailedPassword with date
values for all users entered as 1/1/1754.
Not only is this goofy bullsh!t it is grossly incorrect goofy bullsh!t. I
have used one of my three test users to test getting locked out so I could
learn to use the Unlock method and I certainly did not enter that user's
incorrect credentials on 1/1/1754. I have no idea how the other users have
data has been manipulated either.
What the heck is going on here?
<%= Clinton Gallagher
NET csgallagher AT metromilwaukee.com
URL http://www.metromilwaukee.com/clintongallagher/If a Goofy programmer read the goofy doc before posting goofy messages, he
would fined that 1/1/1754 for the lockout data means it has not been locked
out.
http://msdn2.microsoft.com/en-us/li...ipprovider.aspx
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"clintonG" < csgallagher@.REMOVETHISTEXTmetromilwaukee
.com> wrote in message
news:%230DLIENiGHA.1264@.TK2MSFTNGP05.phx.gbl...
> What's with this software? Every day its a new surprise with some goofy
> bullsh!t.
> I finally make time to try to finish building out ASP.NET 2.0 Membership
> logging and reporting code and today its user data in the SQL Server 2005
> aspnet_Membership table such as LastLockoutDate and FailedPassword with
> date values for all users entered as 1/1/1754.
> Not only is this goofy bullsh!t it is grossly incorrect goofy bullsh!t. I
> have used one of my three test users to test getting locked out so I could
> learn to use the Unlock method and I certainly did not enter that user's
> incorrect credentials on 1/1/1754. I have no idea how the other users have
> data has been manipulated either.
> What the heck is going on here?
> <%= Clinton Gallagher
> NET csgallagher AT metromilwaukee.com
> URL http://www.metromilwaukee.com/clintongallagher/
>|||DOH!!!
Sorry, couldn't resist...|||I don't use the AD Provider but I do see by the document you refer to that
the explanation of this goofy date sh!t is much more lucid and complete than
in other documents I did and have read [1] but still happen to have miss
ed
the pithy sentence that is supposed to pass for documentation.
<%= Clinton Gallagher
NET csgallagher AT metromilwaukee.com
URL http://www.metromilwaukee.com/clintongallagher/
[1]
http://msdn2.microsoft.com/en-us/li...
ckoutdate.aspx
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:etI$pGOiGHA.4512@.TK2MSFTNGP02.phx.gbl...
> If a Goofy programmer read the goofy doc before posting goofy messages, he
> would fined that 1/1/1754 for the lockout data means it has not been
> locked out.
> http://msdn2.microsoft.com/en-us/li...ipprovider.aspx
>
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "clintonG" < csgallagher@.REMOVETHISTEXTmetromilwaukee
.com> wrote in message
> news:%230DLIENiGHA.1264@.TK2MSFTNGP05.phx.gbl...
>
bullsh!t.
I finally make time to try to finish building out ASP.NET 2.0 Membership
logging and reporting code and today its user data in the SQL Server 2005
aspnet_Membership table such as LastLockoutDate and FailedPassword with date
values for all users entered as 1/1/1754.
Not only is this goofy bullsh!t it is grossly incorrect goofy bullsh!t. I
have used one of my three test users to test getting locked out so I could
learn to use the Unlock method and I certainly did not enter that user's
incorrect credentials on 1/1/1754. I have no idea how the other users have
data has been manipulated either.
What the heck is going on here?
<%= Clinton Gallagher
NET csgallagher AT metromilwaukee.com
URL http://www.metromilwaukee.com/clintongallagher/If a Goofy programmer read the goofy doc before posting goofy messages, he
would fined that 1/1/1754 for the lockout data means it has not been locked
out.
http://msdn2.microsoft.com/en-us/li...ipprovider.aspx
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"clintonG" < csgallagher@.REMOVETHISTEXTmetromilwaukee
.com> wrote in message
news:%230DLIENiGHA.1264@.TK2MSFTNGP05.phx.gbl...
> What's with this software? Every day its a new surprise with some goofy
> bullsh!t.
> I finally make time to try to finish building out ASP.NET 2.0 Membership
> logging and reporting code and today its user data in the SQL Server 2005
> aspnet_Membership table such as LastLockoutDate and FailedPassword with
> date values for all users entered as 1/1/1754.
> Not only is this goofy bullsh!t it is grossly incorrect goofy bullsh!t. I
> have used one of my three test users to test getting locked out so I could
> learn to use the Unlock method and I certainly did not enter that user's
> incorrect credentials on 1/1/1754. I have no idea how the other users have
> data has been manipulated either.
> What the heck is going on here?
> <%= Clinton Gallagher
> NET csgallagher AT metromilwaukee.com
> URL http://www.metromilwaukee.com/clintongallagher/
>|||DOH!!!
Sorry, couldn't resist...|||I don't use the AD Provider but I do see by the document you refer to that
the explanation of this goofy date sh!t is much more lucid and complete than
in other documents I did and have read [1] but still happen to have miss
ed
the pithy sentence that is supposed to pass for documentation.
<%= Clinton Gallagher
NET csgallagher AT metromilwaukee.com
URL http://www.metromilwaukee.com/clintongallagher/
[1]
http://msdn2.microsoft.com/en-us/li...
ckoutdate.aspx
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:etI$pGOiGHA.4512@.TK2MSFTNGP02.phx.gbl...
> If a Goofy programmer read the goofy doc before posting goofy messages, he
> would fined that 1/1/1754 for the lockout data means it has not been
> locked out.
> http://msdn2.microsoft.com/en-us/li...ipprovider.aspx
>
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "clintonG" < csgallagher@.REMOVETHISTEXTmetromilwaukee
.com> wrote in message
> news:%230DLIENiGHA.1264@.TK2MSFTNGP05.phx.gbl...
>
Subscribe to:
Posts (Atom)