Report Designer Dynamic Filter

I have a requirement to add the ability to filter a report by partial last name, at the report level (i.e. not at the database server). In case someone else needs to work out how to do this, here is what I did.

Add a Parameter to the report. In my case it is named LastName, is non-queried, allows Null or Blank, and has a default of null.

Add a filter to the dataset that contains the field to be searched. Set its Expression to:
=IIF(Parameters!LastName.Value = System.DBNull.Value OR Parameters!LastName.Value = "",
Fields!LastName.Value, Nothing) ,
its operator to "="
and its value to =IIF(Parameters!LastName.Value = Nothing OR Parameters!LastName.Value = "", Nothing, Parameters!LastName.Value & "*")

voila!

Helen

I'm not sure I fully understand. What exactly does this do?

Would this have the same effect as using a query with a parameter for lastname (@.lastname) where lastname LIKE @.lastname + "%"?

|||

It allows me to make entering a value for the parameter optional. If the user does not want to filter by last name, my filter expression still has to work. I got it to work by using an expression for both the filter and its value, and returning Nothing for both when the value is null or empty.

When using an expression for the filter, the LIKE option for the comparator is disabled, so I had to use = as the operator.

Report Builder problem with no All level on Scenario?

At first glance, this appears to be a bug in Reporting Services...
I have a 2005 cube with a Scenario dimension. On the Scenario attribute I
set IsAggregatable to False (since it doesn't make sense to add Actuals and
Budgets). This effectively removes the All level, as I understand it. I've
set the DefaultMember to be [Scenario].[Scenario].[Actual]. Now I create a
datasource in SSRS and generate a model off it. When I build a Report Builder
report off the model, I have a problem. If the report does not specify
scenario as a row, column, or filter, then the MDX that gets generated
(captured this via Profiler) starts...
WITH
MEMBER [Scenario].[Scenario].[Agg_0] AS 'Aggregate( [CS_Set0] ) '
SET [CS_Set0] AS [Scenario].[Scenario].Levels(0).Members
And since [Agg_0] is used in the body of the query inside an Exists()
function, it results in the query returning no cells (so the report says that
no data was returned). This may be a problem with the engine that translates
a model query into MDX. For some reason it's not paying attention to the
DefaultMember. (That's why I posted to this newsgroup, not the SSAS
newsgroup.)
When I flip IsAggregatable back to True such that there's an All level,
everything works fine. It gives me the correct numbers. But I don't want to
show an All level for the Scenario dimension.
Please let me know if you have any suggestions or if you can confirm this is
a bug. And please let me know if the SSRS guys feel this is an SSAS issue
that should be posted in that newsgroup.
(As a side note, though I get the right numbers by turning IsAggregatable to
True, I think the MDX is still not quite right because it references
[Scenario].[Scenario].[All] in the Exists function when it really should be
referencing [Scenario].CurrentMember. But that's another topic and not nearly
as crucial. The worst that could happen there is that you show some unneeded
rows. And I may be wrong on whether it should use CurrentMember.)"FurmanGG" wrote:
> At first glance, this appears to be a bug in Reporting Services...
> I have a 2005 cube with a Scenario dimension. On the Scenario attribute I
> set IsAggregatable to False (since it doesn't make sense to add Actuals and
> Budgets). This effectively removes the All level, as I understand it. I've
> set the DefaultMember to be [Scenario].[Scenario].[Actual]. Now I create a
> datasource in SSRS and generate a model off it. When I build a Report Builder
> report off the model, I have a problem. If the report does not specify
> scenario as a row, column, or filter, then the MDX that gets generated
> (captured this via Profiler) starts...
> WITH
> MEMBER [Scenario].[Scenario].[Agg_0] AS 'Aggregate( [CS_Set0] ) '
> SET [CS_Set0] AS [Scenario].[Scenario].Levels(0).Members
> And since [Agg_0] is used in the body of the query inside an Exists()
> function, it results in the query returning no cells (so the report says that
> no data was returned). This may be a problem with the engine that translates
> a model query into MDX. For some reason it's not paying attention to the
> DefaultMember. (That's why I posted to this newsgroup, not the SSAS
> newsgroup.)
> When I flip IsAggregatable back to True such that there's an All level,
> everything works fine. It gives me the correct numbers. But I don't want to
> show an All level for the Scenario dimension.
> Please let me know if you have any suggestions or if you can confirm this is
> a bug. And please let me know if the SSRS guys feel this is an SSAS issue
> that should be posted in that newsgroup.
> (As a side note, though I get the right numbers by turning IsAggregatable to
> True, I think the MDX is still not quite right because it references
> [Scenario].[Scenario].[All] in the Exists function when it really should be
> referencing [Scenario].CurrentMember. But that's another topic and not nearly
> as crucial. The worst that could happen there is that you show some unneeded
> rows. And I may be wrong on whether it should use CurrentMember.)|||Hello,
Did you get any response to this problem or find any solution? I have about
the same problem; I am building an OLAP cube with a time dimension and stock
number. Those stock figures cannot be aggregated over time, so I set the
IsAggregatable option on the time dimension to False. When I do that, Report
Builder does not work as I would expect...
Thanks, Hans.
"FurmanGG" wrote:
> At first glance, this appears to be a bug in Reporting Services...
> I have a 2005 cube with a Scenario dimension. On the Scenario attribute I
> set IsAggregatable to False (since it doesn't make sense to add Actuals and
> Budgets). This effectively removes the All level, as I understand it. I've
> set the DefaultMember to be [Scenario].[Scenario].[Actual]. Now I create a
> datasource in SSRS and generate a model off it. When I build a Report Builder
> report off the model, I have a problem. If the report does not specify
> scenario as a row, column, or filter, then the MDX that gets generated
> (captured this via Profiler) starts...
> WITH
> MEMBER [Scenario].[Scenario].[Agg_0] AS 'Aggregate( [CS_Set0] ) '
> SET [CS_Set0] AS [Scenario].[Scenario].Levels(0).Members
> And since [Agg_0] is used in the body of the query inside an Exists()
> function, it results in the query returning no cells (so the report says that
> no data was returned). This may be a problem with the engine that translates
> a model query into MDX. For some reason it's not paying attention to the
> DefaultMember. (That's why I posted to this newsgroup, not the SSAS
> newsgroup.)
> When I flip IsAggregatable back to True such that there's an All level,
> everything works fine. It gives me the correct numbers. But I don't want to
> show an All level for the Scenario dimension.
> Please let me know if you have any suggestions or if you can confirm this is
> a bug. And please let me know if the SSRS guys feel this is an SSAS issue
> that should be posted in that newsgroup.
> (As a side note, though I get the right numbers by turning IsAggregatable to
> True, I think the MDX is still not quite right because it references
> [Scenario].[Scenario].[All] in the Exists function when it really should be
> referencing [Scenario].CurrentMember. But that's another topic and not nearly
> as crucial. The worst that could happen there is that you show some unneeded
> rows. And I may be wrong on whether it should use CurrentMember.)|||Should be fixed in SP1...
http://lab.msdn.microsoft.com/ProductFeedback/viewfeedback.aspx?feedbackid=77da7b11-f20a-41ee-a18a-a74fd5ac4650
"Hans Geurtsen" wrote:
> Hello,
> Did you get any response to this problem or find any solution? I have about
> the same problem; I am building an OLAP cube with a time dimension and stock
> number. Those stock figures cannot be aggregated over time, so I set the
> IsAggregatable option on the time dimension to False. When I do that, Report
> Builder does not work as I would expect...
> Thanks, Hans.
> "FurmanGG" wrote:
> > At first glance, this appears to be a bug in Reporting Services...
> >
> > I have a 2005 cube with a Scenario dimension. On the Scenario attribute I
> > set IsAggregatable to False (since it doesn't make sense to add Actuals and
> > Budgets). This effectively removes the All level, as I understand it. I've
> > set the DefaultMember to be [Scenario].[Scenario].[Actual]. Now I create a
> > datasource in SSRS and generate a model off it. When I build a Report Builder
> > report off the model, I have a problem. If the report does not specify
> > scenario as a row, column, or filter, then the MDX that gets generated
> > (captured this via Profiler) starts...
> >
> > WITH
> > MEMBER [Scenario].[Scenario].[Agg_0] AS 'Aggregate( [CS_Set0] ) '
> > SET [CS_Set0] AS [Scenario].[Scenario].Levels(0).Members
> >
> > And since [Agg_0] is used in the body of the query inside an Exists()
> > function, it results in the query returning no cells (so the report says that
> > no data was returned). This may be a problem with the engine that translates
> > a model query into MDX. For some reason it's not paying attention to the
> > DefaultMember. (That's why I posted to this newsgroup, not the SSAS
> > newsgroup.)
> >
> > When I flip IsAggregatable back to True such that there's an All level,
> > everything works fine. It gives me the correct numbers. But I don't want to
> > show an All level for the Scenario dimension.
> >
> > Please let me know if you have any suggestions or if you can confirm this is
> > a bug. And please let me know if the SSRS guys feel this is an SSAS issue
> > that should be posted in that newsgroup.
> >
> > (As a side note, though I get the right numbers by turning IsAggregatable to
> > True, I think the MDX is still not quite right because it references
> > [Scenario].[Scenario].[All] in the Exists function when it really should be
> > referencing [Scenario].CurrentMember. But that's another topic and not nearly
> > as crucial. The worst that could happen there is that you show some unneeded
> > rows. And I may be wrong on whether it should use CurrentMember.)

Report builder and custom security

We need to implement SQL Server 2005 Report Builder using our own security
model. We use application level authentication, in which a user ID and
password is verified against a record in the sql server database. So, we
don't use Windows Authentication. The problem is that we need to implement
the reporting builder as our ad-hoc reporting tool, but we need each user to
have his own private folder on the server. I've found only four articles on
http://msdn2.microsoft.com which talks about custom security extension, but
none of those is even close to what I'm looking for. I'm sure that there're
folks out there who've done this before.
Any suggestion or lead will be greatly appreciated.
Thanks,
Gilgameshhave you activated the "My Reports" option in reporting services?
this create a /My Reports folder and each user will have a private folder.
"Gilgamesh" <gilgamesh4ever@.aol.com> wrote in message
news:ONYLrGK0HHA.5644@.TK2MSFTNGP05.phx.gbl...
> We need to implement SQL Server 2005 Report Builder using our own security
> model. We use application level authentication, in which a user ID and
> password is verified against a record in the sql server database. So, we
> don't use Windows Authentication. The problem is that we need to implement
> the reporting builder as our ad-hoc reporting tool, but we need each user
> to have his own private folder on the server. I've found only four
> articles on http://msdn2.microsoft.com which talks about custom security
> extension, but none of those is even close to what I'm looking for. I'm
> sure that there're folks out there who've done this before.
> Any suggestion or lead will be greatly appreciated.
> Thanks,
> Gilgamesh
>|||Yes, I have. The problem is that My Reports works only if you use Windows
Autehtication. As I explained in the posting, we use database authetication.
-G
"Jeje" <willgart@.hotmail.com> wrote in message
news:Oz1e7LM0HHA.1164@.TK2MSFTNGP02.phx.gbl...
> have you activated the "My Reports" option in reporting services?
> this create a /My Reports folder and each user will have a private folder.
>
> "Gilgamesh" <gilgamesh4ever@.aol.com> wrote in message
> news:ONYLrGK0HHA.5644@.TK2MSFTNGP05.phx.gbl...
>> We need to implement SQL Server 2005 Report Builder using our own
>> security model. We use application level authentication, in which a user
>> ID and password is verified against a record in the sql server database.
>> So, we don't use Windows Authentication. The problem is that we need to
>> implement the reporting builder as our ad-hoc reporting tool, but we need
>> each user to have his own private folder on the server. I've found only
>> four articles on http://msdn2.microsoft.com which talks about custom
>> security extension, but none of those is even close to what I'm looking
>> for. I'm sure that there're folks out there who've done this before.
>> Any suggestion or lead will be greatly appreciated.
>> Thanks,
>> Gilgamesh
>>|||Have you implemented custom security in Reporting Services? I don't use
Report Builder but in the end you end up with a RDL just like if it had been
designed in Report Designer.
So, my question is, do you have your custom security implemented in any way
with RS? That is the first thing you will need to do.
http://msdn2.microsoft.com/en-us/library/ms152825.aspx
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Gilgamesh" <gilgamesh4ever@.aol.com> wrote in message
news:ercOBrW0HHA.4236@.TK2MSFTNGP06.phx.gbl...
> Yes, I have. The problem is that My Reports works only if you use Windows
> Autehtication. As I explained in the posting, we use database
> authetication.
> -G
> "Jeje" <willgart@.hotmail.com> wrote in message
> news:Oz1e7LM0HHA.1164@.TK2MSFTNGP02.phx.gbl...
>> have you activated the "My Reports" option in reporting services?
>> this create a /My Reports folder and each user will have a private
>> folder.
>>
>> "Gilgamesh" <gilgamesh4ever@.aol.com> wrote in message
>> news:ONYLrGK0HHA.5644@.TK2MSFTNGP05.phx.gbl...
>> We need to implement SQL Server 2005 Report Builder using our own
>> security model. We use application level authentication, in which a user
>> ID and password is verified against a record in the sql server database.
>> So, we don't use Windows Authentication. The problem is that we need to
>> implement the reporting builder as our ad-hoc reporting tool, but we
>> need each user to have his own private folder on the server. I've found
>> only four articles on http://msdn2.microsoft.com which talks about
>> custom security extension, but none of those is even close to what I'm
>> looking for. I'm sure that there're folks out there who've done this
>> before.
>> Any suggestion or lead will be greatly appreciated.
>> Thanks,
>> Gilgamesh
>>
>|||Bruce
ok, i need to do the same thing. But i am having some trouble with
configuring the secruity extension (Forms Authenication). i have an
question on the User Accounts database part.
The instructions say to replace the "LocalMachine" towards the end of
the createuserstore.sql. But i don't see any mention of that in the
script at all. Any ideas?
INSTRUCTIONS:
Locate "LocalMachine" towards the end of the script and replace it
with your own computer name. For Windows 2003 users, replace
LocalMachine\ASPNET with NT AUTHORITY\NETWORK SERVICE (except when in
IIS 5 compatibility mode).
createuserstore SCRIPT:
exec ('sp_grantlogin [' + @.ASPUserName + ']');
-- Add a database login for the UserAccounts database for the ASPNET
account
exec ('sp_grantdbaccess [' + @.ASPUserName + ']');
-- Grant execute permissions to the LookupUser and RegisterUser stored
procs
exec ('grant execute on LookupUser to [' + @.ASPUserName + ']');
exec ('grant execute on RegisterUser to [' + @.ASPUserName + ']');
------
Have you implemented custom security in Reporting Services? I don't
use
Report Builder but in the end you end up with a RDL just like if it
had been
designed in Report Designer.
So, my question is, do you have your custom security implemented in
any way
with RS? That is the first thing you will need to do.
http://msdn2.microsoft.com/en-us/library/ms152825.aspx
On Jul 29, 3:15 pm, "Bruce L-C [MVP]" <bruce_lcNOS...@.hotmail.com>
wrote:
> Have you implemented custom security in Reporting Services? I don't use
> Report Builder but in the end you end up with a RDL just like if it had been
> designed in Report Designer.
> So, my question is, do you have your custom security implemented in any way
> with RS? That is the first thing you will need to do.http://msdn2.microsoft.com/en-us/library/ms152825.aspx
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Gilgamesh" <gilgamesh4e...@.aol.com> wrote in message
> news:ercOBrW0HHA.4236@.TK2MSFTNGP06.phx.gbl...
>
> > Yes, I have. The problem is that My Reports works only if you use Windows
> > Autehtication. As I explained in the posting, we use database
> > authetication.
> > -G
> > "Jeje" <willg...@.hotmail.com> wrote in message
> >news:Oz1e7LM0HHA.1164@.TK2MSFTNGP02.phx.gbl...
> >> have you activated the "My Reports" option in reporting services?
> >> this create a /My Reports folder and each user will have a private
> >> folder.
> >> "Gilgamesh" <gilgamesh4e...@.aol.com> wrote in message
> >>news:ONYLrGK0HHA.5644@.TK2MSFTNGP05.phx.gbl...
> >> We need to implement SQL Server 2005 Report Builder using our own
> >> security model. We use application level authentication, in which a user
> >> ID and password is verified against a record in the sql server database.
> >> So, we don't use Windows Authentication. The problem is that we need to
> >> implement the reporting builder as our ad-hoc reporting tool, but we
> >> need each user to have his own private folder on the server. I've found
> >> only four articles onhttp://msdn2.microsoft.comwhich talks about
> >> custom security extension, but none of those is even close to what I'm
> >> looking for. I'm sure that there're folks out there who've done this
> >> before.
> >> Any suggestion or lead will be greatly appreciated.
> >> Thanks,
> >> Gilgamesh- Hide quoted text -
> - Show quoted text -|||Sorry, I have not implemented this. I suggest a separate post specifically
about that. Also, you might want to post it at the web based forums as well.
http://forums.microsoft.com/msdn/showforum.aspx?forumid=82&siteid=1
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Ryan Swann" <swannryan@.gmail.com> wrote in message
news:1185807504.059515.124770@.57g2000hsv.googlegroups.com...
> Bruce
> ok, i need to do the same thing. But i am having some trouble with
> configuring the secruity extension (Forms Authenication). i have an
> question on the User Accounts database part.
> The instructions say to replace the "LocalMachine" towards the end of
> the createuserstore.sql. But i don't see any mention of that in the
> script at all. Any ideas?
>
> INSTRUCTIONS:
> Locate "LocalMachine" towards the end of the script and replace it
> with your own computer name. For Windows 2003 users, replace
> LocalMachine\ASPNET with NT AUTHORITY\NETWORK SERVICE (except when in
> IIS 5 compatibility mode).
> createuserstore SCRIPT:
>
> exec ('sp_grantlogin [' + @.ASPUserName + ']');
> -- Add a database login for the UserAccounts database for the ASPNET
> account
> exec ('sp_grantdbaccess [' + @.ASPUserName + ']');
> -- Grant execute permissions to the LookupUser and RegisterUser stored
> procs
> exec ('grant execute on LookupUser to [' + @.ASPUserName + ']');
> exec ('grant execute on RegisterUser to [' + @.ASPUserName + ']');
> ------
> Have you implemented custom security in Reporting Services? I don't
> use
> Report Builder but in the end you end up with a RDL just like if it
> had been
> designed in Report Designer.
> So, my question is, do you have your custom security implemented in
> any way
> with RS? That is the first thing you will need to do.
> http://msdn2.microsoft.com/en-us/library/ms152825.aspx
>
>
>
>
> On Jul 29, 3:15 pm, "Bruce L-C [MVP]" <bruce_lcNOS...@.hotmail.com>
> wrote:
>> Have you implemented custom security in Reporting Services? I don't use
>> Report Builder but in the end you end up with a RDL just like if it had
>> been
>> designed in Report Designer.
>> So, my question is, do you have your custom security implemented in any
>> way
>> with RS? That is the first thing you will need to
>> do.http://msdn2.microsoft.com/en-us/library/ms152825.aspx
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Gilgamesh" <gilgamesh4e...@.aol.com> wrote in message
>> news:ercOBrW0HHA.4236@.TK2MSFTNGP06.phx.gbl...
>>
>> > Yes, I have. The problem is that My Reports works only if you use
>> > Windows
>> > Autehtication. As I explained in the posting, we use database
>> > authetication.
>> > -G
>> > "Jeje" <willg...@.hotmail.com> wrote in message
>> >news:Oz1e7LM0HHA.1164@.TK2MSFTNGP02.phx.gbl...
>> >> have you activated the "My Reports" option in reporting services?
>> >> this create a /My Reports folder and each user will have a private
>> >> folder.
>> >> "Gilgamesh" <gilgamesh4e...@.aol.com> wrote in message
>> >>news:ONYLrGK0HHA.5644@.TK2MSFTNGP05.phx.gbl...
>> >> We need to implement SQL Server 2005 Report Builder using our own
>> >> security model. We use application level authentication, in which a
>> >> user
>> >> ID and password is verified against a record in the sql server
>> >> database.
>> >> So, we don't use Windows Authentication. The problem is that we need
>> >> to
>> >> implement the reporting builder as our ad-hoc reporting tool, but we
>> >> need each user to have his own private folder on the server. I've
>> >> found
>> >> only four articles onhttp://msdn2.microsoft.comwhich talks about
>> >> custom security extension, but none of those is even close to what
>> >> I'm
>> >> looking for. I'm sure that there're folks out there who've done this
>> >> before.
>> >> Any suggestion or lead will be greatly appreciated.
>> >> Thanks,
>> >> Gilgamesh- Hide quoted text -
>> - Show quoted text -
>|||I got evreything working, let me know if someone needs some help with it
"Bruce L-C [MVP]" wrote:
> Sorry, I have not implemented this. I suggest a separate post specifically
> about that. Also, you might want to post it at the web based forums as well.
> http://forums.microsoft.com/msdn/showforum.aspx?forumid=82&siteid=1
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Ryan Swann" <swannryan@.gmail.com> wrote in message
> news:1185807504.059515.124770@.57g2000hsv.googlegroups.com...
> > Bruce
> >
> > ok, i need to do the same thing. But i am having some trouble with
> > configuring the secruity extension (Forms Authenication). i have an
> > question on the User Accounts database part.
> >
> > The instructions say to replace the "LocalMachine" towards the end of
> > the createuserstore.sql. But i don't see any mention of that in the
> > script at all. Any ideas?
> >
> >
> > INSTRUCTIONS:
> >
> > Locate "LocalMachine" towards the end of the script and replace it
> > with your own computer name. For Windows 2003 users, replace
> > LocalMachine\ASPNET with NT AUTHORITY\NETWORK SERVICE (except when in
> > IIS 5 compatibility mode).
> >
> > createuserstore SCRIPT:
> >
> >
> > exec ('sp_grantlogin [' + @.ASPUserName + ']');
> >
> > -- Add a database login for the UserAccounts database for the ASPNET
> > account
> > exec ('sp_grantdbaccess [' + @.ASPUserName + ']');
> >
> > -- Grant execute permissions to the LookupUser and RegisterUser stored
> > procs
> > exec ('grant execute on LookupUser to [' + @.ASPUserName + ']');
> > exec ('grant execute on RegisterUser to [' + @.ASPUserName + ']');
> >
> > ------
> > Have you implemented custom security in Reporting Services? I don't
> > use
> > Report Builder but in the end you end up with a RDL just like if it
> > had been
> > designed in Report Designer.
> >
> > So, my question is, do you have your custom security implemented in
> > any way
> > with RS? That is the first thing you will need to do.
> > http://msdn2.microsoft.com/en-us/library/ms152825.aspx
> >
> >
> >
> >
> >
> >
> >
> >
> > On Jul 29, 3:15 pm, "Bruce L-C [MVP]" <bruce_lcNOS...@.hotmail.com>
> > wrote:
> >> Have you implemented custom security in Reporting Services? I don't use
> >> Report Builder but in the end you end up with a RDL just like if it had
> >> been
> >> designed in Report Designer.
> >>
> >> So, my question is, do you have your custom security implemented in any
> >> way
> >> with RS? That is the first thing you will need to
> >> do.http://msdn2.microsoft.com/en-us/library/ms152825.aspx
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Gilgamesh" <gilgamesh4e...@.aol.com> wrote in message
> >>
> >> news:ercOBrW0HHA.4236@.TK2MSFTNGP06.phx.gbl...
> >>
> >>
> >>
> >> > Yes, I have. The problem is that My Reports works only if you use
> >> > Windows
> >> > Autehtication. As I explained in the posting, we use database
> >> > authetication.
> >> > -G
> >>
> >> > "Jeje" <willg...@.hotmail.com> wrote in message
> >> >news:Oz1e7LM0HHA.1164@.TK2MSFTNGP02.phx.gbl...
> >> >> have you activated the "My Reports" option in reporting services?
> >> >> this create a /My Reports folder and each user will have a private
> >> >> folder.
> >>
> >> >> "Gilgamesh" <gilgamesh4e...@.aol.com> wrote in message
> >> >>news:ONYLrGK0HHA.5644@.TK2MSFTNGP05.phx.gbl...
> >> >> We need to implement SQL Server 2005 Report Builder using our own
> >> >> security model. We use application level authentication, in which a
> >> >> user
> >> >> ID and password is verified against a record in the sql server
> >> >> database.
> >> >> So, we don't use Windows Authentication. The problem is that we need
> >> >> to
> >> >> implement the reporting builder as our ad-hoc reporting tool, but we
> >> >> need each user to have his own private folder on the server. I've
> >> >> found
> >> >> only four articles onhttp://msdn2.microsoft.comwhich talks about
> >> >> custom security extension, but none of those is even close to what
> >> >> I'm
> >> >> looking for. I'm sure that there're folks out there who've done this
> >> >> before.
> >>
> >> >> Any suggestion or lead will be greatly appreciated.
> >>
> >> >> Thanks,
> >> >> Gilgamesh- Hide quoted text -
> >>
> >> - Show quoted text -
> >
> >
>
>