FIXED THE PROBLEM I AM GETTING

Hello Friends

I am very glad to tell all u ppl that i ve got the solution to my problem at last
I ve just posted my problem(few mins back) in which i was getting problem with connecting to the ASP.NET Web application. I have made a new user on sql through SQL Enterprise Manager as <machinename>\ASPNET, and my problem gets solved

sorry to bother u all

Regards
BSSGlad you got this worked out. Next time please be sure to reply to your original post letting people know the problem is solved. :-)

Regards,
Terri

first day of week by Week Number

I was looking for a solution for this problem - but none of what I
found in Internet helped - so finally I made something myself ( based a
little bit on someone's idea). I hope it will be useful to someone - or
maybe u'll see some bugs in it? please report.
there 2 assumptions
1. before executing this function u SET DATEFIRST 1
2. u have already an IsoW function implemented ( found in Books
Online as example for CREATE FUNCTION)
create function fdaywk (@.year int, @.w int )
returns datetime
as
begin
declare @.date datetime
begin
set @.date = cast('01/01/' + cast(@.year as char(4))as datetime)
if datepart(dw,@.date)>4
set @.date = @.date+8-datepart(dw,@.date)
else
set @.date= @.date-datepart(dw,@.date)+1
set @.date = dateadd(wk, @.w-1, @.date)
end
return(@.date)
endHi,
your solution wont work on other servers than US or english one, using
US regional settings.
The code in cause is :
set @.date = cast('01/01/' + cast(@.year as char(4))as datetime)
You must use the short ISO date encode wich is SQL Server World Wide
portable solution :
YYYYMMDD HH:MM:SS.nnn
Try it :
SELECT CAST('20050225 11:23:17.852' AS DATETIME) AS DT
This datetime format is corresponding to CONVERT(... 121)
A +
tomek a crit :
> I was looking for a solution for this problem - but none of what I
> found in Internet helped - so finally I made something myself ( based a
> little bit on someone's idea). I hope it will be useful to someone - or
> maybe u'll see some bugs in it? please report.
> there 2 assumptions
> 1. before executing this function u SET DATEFIRST 1
> 2. u have already an IsoW function implemented ( found in Books
> Online as example for CREATE FUNCTION)
> create function fdaywk (@.year int, @.w int )
> returns datetime
> as
> begin
> declare @.date datetime
> begin
> set @.date = cast('01/01/' + cast(@.year as char(4))as datetime)
> if datepart(dw,@.date)>4
> set @.date = @.date+8-datepart(dw,@.date)
> else
> set @.date= @.date-datepart(dw,@.date)+1
> set @.date = dateadd(wk, @.w-1, @.date)
> end
> return(@.date)
> end
>
Frdric BROUARD, MVP SQL Server, expert bases de donnes et langage SQL
Le site sur le langage SQL et les SGBDR : http://sqlpro.developpez.com
Audit, conseil, expertise, formation, modlisation, tuning, optimisation
********************* http://www.datasapiens.com ***********************

Firefox and other non-IE browsers(again)

I've seen many posts about lack of non-IE browser compatibility, but still no solution (MyIEtab ISN'T a solution). The CSS fix solves it partially, but not completely, and the fix of putting a rectangle in the top is just a joke.

Currently my reports can't be browsed by Firefox and other Mac browsers, and that's going to be a stopper for further using of SSRS in the future in my company. I was expecting SP2 to do something about this, but it hasn't solved anything. I'm sure it's a very easy patch for MS, but by maintaining this (artificial?) limitation they're going to make us move from SSRS and even the full SQL Server stack for future projects.

Any other *real* solution, other than CSS and big rectangle in the top of the report?This could be a huge problem for my client also.

I wonder how many customers Microsoft lost over this. I know it is free and all (with Sql Server), but doesn't do much for customer confidence.

Firefox and other non-IE browsers(again)

I've seen many posts about lack of non-IE browser compatibility, but still no solution (MyIEtab ISN'T a solution). The CSS fix solves it partially, but not completely, and the fix of putting a rectangle in the top is just a joke.

Currently my reports can't be browsed by Firefox and other Mac browsers, and that's going to be a stopper for further using of SSRS in the future in my company. I was expecting SP2 to do something about this, but it hasn't solved anything. I'm sure it's a very easy patch for MS, but by maintaining this (artificial?) limitation they're going to make us move from SSRS and even the full SQL Server stack for future projects.

Any other *real* solution, other than CSS and big rectangle in the top of the report?
This could be a huge problem for my client also.

I wonder how many customers Microsoft lost over this. I know it is free and all (with Sql Server), but doesn't do much for customer confidence.