Hi
I am trying to seth the background colour of a textbox to either red or
green depending on the multiple values in my dataset.
Each row of my dataset has a boolean value for Pass. The background colour
of the text box needs to be green if all rows in my dataset have a Pass
value of True but if only one row in the dataset has a Pass value of False,
the background colour needs to be set to red.
I have tries the obvious expression =IIF(Fields!Pass.Value = True, "Green",
"Red") but this will set the background to green again if their is a row in
the dataset with a Pass value of True after the row which had the Pass value
of False.
I have also tried counting the number of rows with a specific value but this
does not seem to work.
=IIF(count(Fields!Pass.Value = False) = 0, "Green", "Red")
Does anyone have any ideas how to get what I want?
Thanks
Lewis Holmes
eNateTry this for multiple values:
=iif(Sum(iif(Fields!Pass.Value, 1, 0)) > 0, "Green", "Red")
-- Robert
This posting is provided "AS IS" with no warranties, and confers no rights.
"l.holmes" <enate@.newsgroups.nospam> wrote in message
news:uMp0e%23J2FHA.3816@.TK2MSFTNGP14.phx.gbl...
> Hi
> I am trying to seth the background colour of a textbox to either red or
> green depending on the multiple values in my dataset.
> Each row of my dataset has a boolean value for Pass. The background colour
> of the text box needs to be green if all rows in my dataset have a Pass
> value of True but if only one row in the dataset has a Pass value of
> False, the background colour needs to be set to red.
> I have tries the obvious expression =IIF(Fields!Pass.Value = True,
> "Green", "Red") but this will set the background to green again if their
> is a row in the dataset with a Pass value of True after the row which had
> the Pass value of False.
> I have also tried counting the number of rows with a specific value but
> this does not seem to work.
> =IIF(count(Fields!Pass.Value = False) = 0, "Green", "Red")
> Does anyone have any ideas how to get what I want?
> Thanks
> Lewis Holmes
> eNate
>|||Hi Robert
Thanks for the reply.
I do not think this will work still. For example say my dataset has three
rows which have Pass values of True, False and True.
As i understand, using this expression for the first row, the expression
will evaluate to Green as Value is True. Then for the second row the
expression will evaluate to Red as value is False (this is all correct).
However, my problem is that now after evaluating the expression for third
row, the value returned will be Green as Value is true and so sum returns 1.
This is not the behaviour I want as the background colour should be Red if
one or more of the Pass values is false.Using this expression, the result
from the third row is setting the background colour back to green.
Hope this explains the problem better.
Kind Regards
Lewis Holmes
eNate
"Robert Bruckner [MSFT]" <robruc@.online.microsoft.com> wrote in message
news:eO1NksR2FHA.3880@.TK2MSFTNGP12.phx.gbl...
> Try this for multiple values:
> =iif(Sum(iif(Fields!Pass.Value, 1, 0)) > 0, "Green", "Red")
> -- Robert
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "l.holmes" <enate@.newsgroups.nospam> wrote in message
> news:uMp0e%23J2FHA.3816@.TK2MSFTNGP14.phx.gbl...
>> Hi
>> I am trying to seth the background colour of a textbox to either red or
>> green depending on the multiple values in my dataset.
>> Each row of my dataset has a boolean value for Pass. The background
>> colour of the text box needs to be green if all rows in my dataset have a
>> Pass value of True but if only one row in the dataset has a Pass value of
>> False, the background colour needs to be set to red.
>> I have tries the obvious expression =IIF(Fields!Pass.Value = True,
>> "Green", "Red") but this will set the background to green again if their
>> is a row in the dataset with a Pass value of True after the row which had
>> the Pass value of False.
>> I have also tried counting the number of rows with a specific value but
>> this does not seem to work.
>> =IIF(count(Fields!Pass.Value = False) = 0, "Green", "Red")
>> Does anyone have any ideas how to get what I want?
>> Thanks
>> Lewis Holmes
>> eNate
>|||Hi Lewis,
In you case, I understood if there is one backgroup to be Red (false), you
want all following backgroup to be shown as Red (false). If I have
misunderstood your concern, please feel free to point it out.
I am afraid there won't be an easy to accomplish this. You may try using
.net assembly to identify the color according to row number with custom
function.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
Showing posts with label background. Show all posts
Showing posts with label background. Show all posts
Wednesday, March 7, 2012
Express, Can I really redistribute this with our app?
SQL 2005 Express, Can I really redistribute this with our app?
Background: We sell a software program to Fortune 1000, always previously
required clients to use or obtain at least SQL 2000 Standard, always a
tedious process on their end, ie budgets, licensing, IT folks, etc.
Our typical client site has about 10 users who use our program, and the SQL
DB on some nearby host server.
Our DB requirements fit Express such as size < 4GB and Ram < 1GB. We don't
do anything too fancy with the DB, about 70 tables, 70 triggers, 140 stored
procedures. We use an embedded ID & PW passed by application, so SQL Login
has to be in there, but we can probably be flexible here.
Is SQL Express really a deployable solution for us? I assume that we can
script stuff like DB creation along with Tables and other needed objects,
allowing a typcial small group of users to get up and running quickly.
Can the DB host be an XP o/s in this scenerio? Do we need Management
Studio Express ?
From what I've read up at ms.com, all of this seems possible, I just can't
believe it would be this easy.
Any and all comments will be greatly appreciated."John" <John@.discussions.microsoft.com> wrote in message
news:936531F0-26FF-432E-A783-AD8264CE486A@.microsoft.com...
> SQL 2005 Express, Can I really redistribute this with our app?
> Background: We sell a software program to Fortune 1000, always previously
> required clients to use or obtain at least SQL 2000 Standard, always a
> tedious process on their end, ie budgets, licensing, IT folks, etc.
> Our typical client site has about 10 users who use our program, and the
> SQL
> DB on some nearby host server.
> Our DB requirements fit Express such as size < 4GB and Ram < 1GB. We
> don't
> do anything too fancy with the DB, about 70 tables, 70 triggers, 140
> stored
> procedures. We use an embedded ID & PW passed by application, so SQL
> Login
> has to be in there, but we can probably be flexible here.
> Is SQL Express really a deployable solution for us? I assume that we can
> script stuff like DB creation along with Tables and other needed objects,
> allowing a typcial small group of users to get up and running quickly.
> Can the DB host be an XP o/s in this scenerio? Do we need Management
> Studio Express ?
> From what I've read up at ms.com, all of this seems possible, I just can't
> believe it would be this easy.
> Any and all comments will be greatly appreciated.
>
Yep, it's that easy. You need to register for redistribution rights
(http://www.microsoft.com/sql/editions/express/redistregister.mspx).
Of course your customers might want to deploy your app on a higher SKU of
SQL Server, and they can always upgrade later.
David|||Thanks David for confirming its that easy.
How about the Windows XP host PC? Is that OK with say about 10 users
accessing data?
And Management Studio Express ? Is a gold release out yet or still CTP?
I'm figuring we'd need to use this for deployment or at least make it
available for clients just in case.
Again, your comments are valuable and appreciated!
John|||"John" <John@.discussions.microsoft.com> wrote in message
news:08D225AB-CB1E-44E4-BF80-D831FA3D57F8@.microsoft.com...
> Thanks David for confirming its that easy.
> How about the Windows XP host PC? Is that OK with say about 10 users
> accessing data?
It will install fine, but SQL Server is a server product, and you should
really run it on a server OS. Even though you don't have to pay a lot for
it you should take the deployment decisions seriously. Especially with
Fortune 1000 customers, their XP desktops are probably managed in a way that
makes them unsuitable for running a server product. Run Windows 2003
Server.
> And Management Studio Express ? Is a gold release out yet or still CTP?
> I'm figuring we'd need to use this for deployment or at least make it
> available for clients just in case.
For development get your staff MSDN or SQL Server Developer Edition. This
will give you full access to all the tools. You can use Management Studio
Express manage your deployed instances.
David
Background: We sell a software program to Fortune 1000, always previously
required clients to use or obtain at least SQL 2000 Standard, always a
tedious process on their end, ie budgets, licensing, IT folks, etc.
Our typical client site has about 10 users who use our program, and the SQL
DB on some nearby host server.
Our DB requirements fit Express such as size < 4GB and Ram < 1GB. We don't
do anything too fancy with the DB, about 70 tables, 70 triggers, 140 stored
procedures. We use an embedded ID & PW passed by application, so SQL Login
has to be in there, but we can probably be flexible here.
Is SQL Express really a deployable solution for us? I assume that we can
script stuff like DB creation along with Tables and other needed objects,
allowing a typcial small group of users to get up and running quickly.
Can the DB host be an XP o/s in this scenerio? Do we need Management
Studio Express ?
From what I've read up at ms.com, all of this seems possible, I just can't
believe it would be this easy.
Any and all comments will be greatly appreciated."John" <John@.discussions.microsoft.com> wrote in message
news:936531F0-26FF-432E-A783-AD8264CE486A@.microsoft.com...
> SQL 2005 Express, Can I really redistribute this with our app?
> Background: We sell a software program to Fortune 1000, always previously
> required clients to use or obtain at least SQL 2000 Standard, always a
> tedious process on their end, ie budgets, licensing, IT folks, etc.
> Our typical client site has about 10 users who use our program, and the
> SQL
> DB on some nearby host server.
> Our DB requirements fit Express such as size < 4GB and Ram < 1GB. We
> don't
> do anything too fancy with the DB, about 70 tables, 70 triggers, 140
> stored
> procedures. We use an embedded ID & PW passed by application, so SQL
> Login
> has to be in there, but we can probably be flexible here.
> Is SQL Express really a deployable solution for us? I assume that we can
> script stuff like DB creation along with Tables and other needed objects,
> allowing a typcial small group of users to get up and running quickly.
> Can the DB host be an XP o/s in this scenerio? Do we need Management
> Studio Express ?
> From what I've read up at ms.com, all of this seems possible, I just can't
> believe it would be this easy.
> Any and all comments will be greatly appreciated.
>
Yep, it's that easy. You need to register for redistribution rights
(http://www.microsoft.com/sql/editions/express/redistregister.mspx).
Of course your customers might want to deploy your app on a higher SKU of
SQL Server, and they can always upgrade later.
David|||Thanks David for confirming its that easy.
How about the Windows XP host PC? Is that OK with say about 10 users
accessing data?
And Management Studio Express ? Is a gold release out yet or still CTP?
I'm figuring we'd need to use this for deployment or at least make it
available for clients just in case.
Again, your comments are valuable and appreciated!
John|||"John" <John@.discussions.microsoft.com> wrote in message
news:08D225AB-CB1E-44E4-BF80-D831FA3D57F8@.microsoft.com...
> Thanks David for confirming its that easy.
> How about the Windows XP host PC? Is that OK with say about 10 users
> accessing data?
It will install fine, but SQL Server is a server product, and you should
really run it on a server OS. Even though you don't have to pay a lot for
it you should take the deployment decisions seriously. Especially with
Fortune 1000 customers, their XP desktops are probably managed in a way that
makes them unsuitable for running a server product. Run Windows 2003
Server.
> And Management Studio Express ? Is a gold release out yet or still CTP?
> I'm figuring we'd need to use this for deployment or at least make it
> available for clients just in case.
For development get your staff MSDN or SQL Server Developer Edition. This
will give you full access to all the tools. You can use Management Studio
Express manage your deployed instances.
David
Friday, February 24, 2012
Exposing data
Hi,
I'm about to enter some new ground. I have a background of web development (
ASP) and SQL Server (network environment only). We have a new ASP.NET applic
ation running a SQL DB. This application is to be put out on the net.
Our network admin wants to buy another SQL licence and have the SQL server s
it outside of our network firewall. I'm more inclined to have the SQL server
inside some sort of DMZ (a topic new to me) and open a port for data access
.
Before I take this argument to the network admin I want to arm myself with t
he necessary knowledge. I guess I'm looking for articles/URLs/tutorials whic
h will teach me how to expose a SQL DB on our network to the internet withou
t risking the secuirty of o
ur network or the SQL box itself.
many thanks
JayGenerally for web apps, the exposure works like this:
One port (or maybe two) on the firewall is open for HTTP (80, and perhaps
443 for SSL).
The web server, BEHIND THE FIREWALL, can talk to the database server. Some
admins even go so far as to put a second firewall between the web and
database servers (which I think is generally overkill). No SQL Server ports
should ever be open on the firewall. And no SQL Server should ever be in a
DMZ! That's just asking for trouble...
Anyway, here's a link with some good information about how to secure a web
app using SQL Server:
http://msdn.microsoft.com/library/d...-us/dnnetsec/ht
ml/openhack.asp
"Jay" <Jay@.wdc.com> wrote in message
news:5D4E06B3-1BC0-4A9B-9215-2C20BC72379D@.microsoft.com...
> Hi,
> I'm about to enter some new ground. I have a background of web development
(ASP) and SQL Server (network environment only). We have a new ASP.NET
application running a SQL DB. This application is to be put out on the net.
> Our network admin wants to buy another SQL licence and have the SQL server
sit outside of our network firewall. I'm more inclined to have the SQL
server inside some sort of DMZ (a topic new to me) and open a port for data
access.
> Before I take this argument to the network admin I want to arm myself with
the necessary knowledge. I guess I'm looking for articles/URLs/tutorials
which will teach me how to expose a SQL DB on our network to the internet
without risking the secuirty of our network or the SQL box itself.
> many thanks
> Jay|||This would not be recommended. SQL should be protected by a firewall.
Consider using ISA server 2000 and publishing SQL to the internet.
1433 is one of the highest scanned ports by hackers.
http://www.microsoft.com/technet/pr...n/sp3sec02.mspx
#XSLTsection126121120120
287932 INF: TCP Ports Needed for Communication to SQL Server Through a
Firewall
http://support.microsoft.com/?id=287932
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Thanks Adam,
Priniting it now... will digest it after my first coffee of the morning.
Jay
I'm about to enter some new ground. I have a background of web development (
ASP) and SQL Server (network environment only). We have a new ASP.NET applic
ation running a SQL DB. This application is to be put out on the net.
Our network admin wants to buy another SQL licence and have the SQL server s
it outside of our network firewall. I'm more inclined to have the SQL server
inside some sort of DMZ (a topic new to me) and open a port for data access
.
Before I take this argument to the network admin I want to arm myself with t
he necessary knowledge. I guess I'm looking for articles/URLs/tutorials whic
h will teach me how to expose a SQL DB on our network to the internet withou
t risking the secuirty of o
ur network or the SQL box itself.
many thanks
JayGenerally for web apps, the exposure works like this:
One port (or maybe two) on the firewall is open for HTTP (80, and perhaps
443 for SSL).
The web server, BEHIND THE FIREWALL, can talk to the database server. Some
admins even go so far as to put a second firewall between the web and
database servers (which I think is generally overkill). No SQL Server ports
should ever be open on the firewall. And no SQL Server should ever be in a
DMZ! That's just asking for trouble...
Anyway, here's a link with some good information about how to secure a web
app using SQL Server:
http://msdn.microsoft.com/library/d...-us/dnnetsec/ht
ml/openhack.asp
"Jay" <Jay@.wdc.com> wrote in message
news:5D4E06B3-1BC0-4A9B-9215-2C20BC72379D@.microsoft.com...
> Hi,
> I'm about to enter some new ground. I have a background of web development
(ASP) and SQL Server (network environment only). We have a new ASP.NET
application running a SQL DB. This application is to be put out on the net.
> Our network admin wants to buy another SQL licence and have the SQL server
sit outside of our network firewall. I'm more inclined to have the SQL
server inside some sort of DMZ (a topic new to me) and open a port for data
access.
> Before I take this argument to the network admin I want to arm myself with
the necessary knowledge. I guess I'm looking for articles/URLs/tutorials
which will teach me how to expose a SQL DB on our network to the internet
without risking the secuirty of our network or the SQL box itself.
> many thanks
> Jay|||This would not be recommended. SQL should be protected by a firewall.
Consider using ISA server 2000 and publishing SQL to the internet.
1433 is one of the highest scanned ports by hackers.
http://www.microsoft.com/technet/pr...n/sp3sec02.mspx
#XSLTsection126121120120
287932 INF: TCP Ports Needed for Communication to SQL Server Through a
Firewall
http://support.microsoft.com/?id=287932
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Thanks Adam,
Priniting it now... will digest it after my first coffee of the morning.
Jay
Subscribe to:
Posts (Atom)