Extended Stored Procedures

The database I am setting up requires a dll file to be added to extended
stored prcoedures - "Using a Microsoft tool such as Enterprise Manager, add
the file to the extended stored prcoedures already installed on SQL Server."
Where/how is this done?
Thank you.
Regards,
DianeYou can run a query like the one below from Query Analyzer. See the Books
Online for more information.
EXEC sp_addextendedproc 'MyFunction', 'MyApp.dll'
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Diane" <Diane@.discussions.microsoft.com> wrote in message
news:508ECDA1-08D8-4593-BAF8-628108DDFF0B@.microsoft.com...
> The database I am setting up requires a dll file to be added to extended
> stored prcoedures - "Using a Microsoft tool such as Enterprise Manager,
> add
> the file to the extended stored prcoedures already installed on SQL
> Server."
> Where/how is this done?
> Thank you.
> Regards,
> Diane|||Diane wrote:
> The database I am setting up requires a dll file to be added to
> extended stored prcoedures - "Using a Microsoft tool such as
> Enterprise Manager, add the file to the extended stored prcoedures
> already installed on SQL Server."
> Where/how is this done?
> Thank you.
> Regards,
> Diane
See "sp_addextendedproc" and "Creating Extended Stored Procedures" in
BOL.
--
David Gugick
Quest Software
www.imceda.com
www.quest.com

Extended Stored Procedures

The database I am setting up requires a dll file to be added to extended
stored prcoedures - "Using a Microsoft tool such as Enterprise Manager, add
the file to the extended stored prcoedures already installed on SQL Server."
Where/how is this done?
Thank you.
Regards,
DianeYou can run a query like the one below from Query Analyzer. See the Books
Online for more information.
EXEC sp_addextendedproc 'MyFunction', 'MyApp.dll'
Hope this helps.
Dan Guzman
SQL Server MVP
"Diane" <Diane@.discussions.microsoft.com> wrote in message
news:508ECDA1-08D8-4593-BAF8-628108DDFF0B@.microsoft.com...
> The database I am setting up requires a dll file to be added to extended
> stored prcoedures - "Using a Microsoft tool such as Enterprise Manager,
> add
> the file to the extended stored prcoedures already installed on SQL
> Server."
> Where/how is this done?
> Thank you.
> Regards,
> Diane|||Diane wrote:
> The database I am setting up requires a dll file to be added to
> extended stored prcoedures - "Using a Microsoft tool such as
> Enterprise Manager, add the file to the extended stored prcoedures
> already installed on SQL Server."
> Where/how is this done?
> Thank you.
> Regards,
> Diane
See "sp_addextendedproc" and "Creating Extended Stored Procedures" in
BOL.
David Gugick
Quest Software
www.imceda.com
www.quest.com

Extended Stored Procedures

The database I am setting up requires a dll file to be added to extended
stored prcoedures - "Using a Microsoft tool such as Enterprise Manager, add
the file to the extended stored prcoedures already installed on SQL Server."
Where/how is this done?
Thank you.
Regards,
Diane
You can run a query like the one below from Query Analyzer. See the Books
Online for more information.
EXEC sp_addextendedproc 'MyFunction', 'MyApp.dll'
Hope this helps.
Dan Guzman
SQL Server MVP
"Diane" <Diane@.discussions.microsoft.com> wrote in message
news:508ECDA1-08D8-4593-BAF8-628108DDFF0B@.microsoft.com...
> The database I am setting up requires a dll file to be added to extended
> stored prcoedures - "Using a Microsoft tool such as Enterprise Manager,
> add
> the file to the extended stored prcoedures already installed on SQL
> Server."
> Where/how is this done?
> Thank you.
> Regards,
> Diane
|||Diane wrote:
> The database I am setting up requires a dll file to be added to
> extended stored prcoedures - "Using a Microsoft tool such as
> Enterprise Manager, add the file to the extended stored prcoedures
> already installed on SQL Server."
> Where/how is this done?
> Thank you.
> Regards,
> Diane
See "sp_addextendedproc" and "Creating Extended Stored Procedures" in
BOL.
David Gugick
Quest Software
www.imceda.com
www.quest.com
sql

extend time out setting

Hi,
I really need some help here. I have a few sql clients that connects to
my sql server through wireless connection. Sometimes, these wireless
connections link is down for a few seconds. When user try to continue
to run some query, the db process dead error message appears. Is the
anyway to extend the time out setting to longer time so that this
problem could be minimise?
Thanks a million.Hi
I think this would be a configuration setting on the wireless adapter rather
than the SQL Server connection. You may want to also try sending some form o
f
keep-alive although this would increase the network traffic!
John
"masterwee@.gmail.com" wrote:

> Hi,
> I really need some help here. I have a few sql clients that connects to
> my sql server through wireless connection. Sometimes, these wireless
> connections link is down for a few seconds. When user try to continue
> to run some query, the db process dead error message appears. Is the
> anyway to extend the time out setting to longer time so that this
> problem could be minimise?
> Thanks a million.
>|||The dbprocess dead error indicates a terminated connection rather than a
timeout. The application needs to be smart enough to attempt to reconnect
following the error.
Hope this helps.
Dan Guzman
SQL Server MVP
<masterwee@.gmail.com> wrote in message
news:1162278624.684826.264940@.m73g2000cwd.googlegroups.com...
> Hi,
> I really need some help here. I have a few sql clients that connects to
> my sql server through wireless connection. Sometimes, these wireless
> connections link is down for a few seconds. When user try to continue
> to run some query, the db process dead error message appears. Is the
> anyway to extend the time out setting to longer time so that this
> problem could be minimise?
> Thanks a million.
>|||I have similar problems on some remote sites. Some are running the client
over ISDN which naturally timesout and should pick up the line again when
there is activity. But when the user generates some activity we get the db
process dead message. We migrated these sites from Sybase which never had
these issues and seemed more robust in these situations.
Is there any config options we can use on the client or server to make the
connections less fickle?
Is there any updated client that might be more reliable?
We are using SQL Server 2000 Sp4 but the client is the one on the original
SQl Server 2000 CD.
Thanks,
"Dan Guzman" wrote:

> The dbprocess dead error indicates a terminated connection rather than a
> timeout. The application needs to be smart enough to attempt to reconnect
> following the error.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> <masterwee@.gmail.com> wrote in message
> news:1162278624.684826.264940@.m73g2000cwd.googlegroups.com...
>|||Hi Marty
Unless you have the SQL Server tools on the client PC then there is no point
in using it on the client. You should make sure that a recent version of MDA
C
is on there, although I don't think this will cure the issue as the server
can not reach the client and it can not instigate the ISDN connection.
As Dan has stated you will need to handle the error and reconnect the client
if you get this error.
Has the client application changed from powerbuilder?
John
"Marty" wrote:
[vbcol=seagreen]
> I have similar problems on some remote sites. Some are running the client
> over ISDN which naturally timesout and should pick up the line again when
> there is activity. But when the user generates some activity we get the db
> process dead message. We migrated these sites from Sybase which never had
> these issues and seemed more robust in these situations.
> Is there any config options we can use on the client or server to make the
> connections less fickle?
> Is there any updated client that might be more reliable?
> We are using SQL Server 2000 Sp4 but the client is the one on the original
> SQl Server 2000 CD.
> Thanks,
>
> "Dan Guzman" wrote:
>|||John,
When any activity happens on the client, it wakes up the ISDN connection and
should carry on where it left off in the application, but it looks like the
Client does not re-connect to the server correctly.
I'm not sure which SQL Server tools you refer to?
As for MDAC, it will be the one on the CD, should there be a later version?
The application is written in C++ not Powerbuilder. It is the database which
has been migrated to SQL Server from Sybase, and the old Sybase Open Client
did not report these errors on the same ISDN line.
Thanks,
M
"John Bell" wrote:
[vbcol=seagreen]
> Hi Marty
> Unless you have the SQL Server tools on the client PC then there is no poi
nt
> in using it on the client. You should make sure that a recent version of M
DAC
> is on there, although I don't think this will cure the issue as the server
> can not reach the client and it can not instigate the ISDN connection.
> As Dan has stated you will need to handle the error and reconnect the clie
nt
> if you get this error.
> Has the client application changed from powerbuilder?
> John
> "Marty" wrote:
>|||Hi Marty
Use the MDAC checker from
http://msdn.microsoft.com/data/ref/mdac/downloads/. MDAC can be updated
through other products such as XP SP1, so you may not be on the same version
at all sites. You will need to change the client application so that if the
error is detected the connection is closed and re-open it. I don't know if
the Open Client has the intellegence to silently reconnect or if it was
sending a keep alive.
John
"Marty" wrote:
[vbcol=seagreen]
> John,
> When any activity happens on the client, it wakes up the ISDN connection a
nd
> should carry on where it left off in the application, but it looks like th
e
> Client does not re-connect to the server correctly.
> I'm not sure which SQL Server tools you refer to?
> As for MDAC, it will be the one on the CD, should there be a later version
?
> The application is written in C++ not Powerbuilder. It is the database whi
ch
> has been migrated to SQL Server from Sybase, and the old Sybase Open Clien
t
> did not report these errors on the same ISDN line.
> Thanks,
> M
>
> "John Bell" wrote:
>

extend time out setting

I have similar problems on some remote sites. Some are running the client
over ISDN which naturally timesout and should pick up the line again when
there is activity. But when the user generates some activity we get the db
process dead message. We migrated these sites from Sybase which never had
these issues and seemed more robust in these situations.
Is there any config options we can use on the client or server to make the
connections less fickle?
Is there any updated client that might be more reliable?
We are using SQL Server 2000 Sp4 but the client is the one on the original
SQl Server 2000 CD.
Thanks,
"Dan Guzman" wrote:

> The dbprocess dead error indicates a terminated connection rather than a
> timeout. The application needs to be smart enough to attempt to reconnect
> following the error.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> <masterwee@.gmail.com> wrote in message
> news:1162278624.684826.264940@.m73g2000cwd.googlegr oups.com...
>
Hi Marty
Unless you have the SQL Server tools on the client PC then there is no point
in using it on the client. You should make sure that a recent version of MDAC
is on there, although I don't think this will cure the issue as the server
can not reach the client and it can not instigate the ISDN connection.
As Dan has stated you will need to handle the error and reconnect the client
if you get this error.
Has the client application changed from powerbuilder?
John
"Marty" wrote:
[vbcol=seagreen]
> I have similar problems on some remote sites. Some are running the client
> over ISDN which naturally timesout and should pick up the line again when
> there is activity. But when the user generates some activity we get the db
> process dead message. We migrated these sites from Sybase which never had
> these issues and seemed more robust in these situations.
> Is there any config options we can use on the client or server to make the
> connections less fickle?
> Is there any updated client that might be more reliable?
> We are using SQL Server 2000 Sp4 but the client is the one on the original
> SQl Server 2000 CD.
> Thanks,
>
> "Dan Guzman" wrote:
|||John,
When any activity happens on the client, it wakes up the ISDN connection and
should carry on where it left off in the application, but it looks like the
Client does not re-connect to the server correctly.
I'm not sure which SQL Server tools you refer to?
As for MDAC, it will be the one on the CD, should there be a later version?
The application is written in C++ not Powerbuilder. It is the database which
has been migrated to SQL Server from Sybase, and the old Sybase Open Client
did not report these errors on the same ISDN line.
Thanks,
M
"John Bell" wrote:
[vbcol=seagreen]
> Hi Marty
> Unless you have the SQL Server tools on the client PC then there is no point
> in using it on the client. You should make sure that a recent version of MDAC
> is on there, although I don't think this will cure the issue as the server
> can not reach the client and it can not instigate the ISDN connection.
> As Dan has stated you will need to handle the error and reconnect the client
> if you get this error.
> Has the client application changed from powerbuilder?
> John
> "Marty" wrote:
|||Hi Marty
Use the MDAC checker from
http://msdn.microsoft.com/data/ref/mdac/downloads/. MDAC can be updated
through other products such as XP SP1, so you may not be on the same version
at all sites. You will need to change the client application so that if the
error is detected the connection is closed and re-open it. I don't know if
the Open Client has the intellegence to silently reconnect or if it was
sending a keep alive.
John
"Marty" wrote:
[vbcol=seagreen]
> John,
> When any activity happens on the client, it wakes up the ISDN connection and
> should carry on where it left off in the application, but it looks like the
> Client does not re-connect to the server correctly.
> I'm not sure which SQL Server tools you refer to?
> As for MDAC, it will be the one on the CD, should there be a later version?
> The application is written in C++ not Powerbuilder. It is the database which
> has been migrated to SQL Server from Sybase, and the old Sybase Open Client
> did not report these errors on the same ISDN line.
> Thanks,
> M
>
> "John Bell" wrote:

extend time out setting

Hi,
I really need some help here. I have a few sql clients that connects to
my sql server through wireless connection. Sometimes, these wireless
connections link is down for a few seconds. When user try to continue
to run some query, the db process dead error message appears. Is the
anyway to extend the time out setting to longer time so that this
problem could be minimise?
Thanks a million.Hi
I think this would be a configuration setting on the wireless adapter rather
than the SQL Server connection. You may want to also try sending some form of
keep-alive although this would increase the network traffic!
John
"masterwee@.gmail.com" wrote:
> Hi,
> I really need some help here. I have a few sql clients that connects to
> my sql server through wireless connection. Sometimes, these wireless
> connections link is down for a few seconds. When user try to continue
> to run some query, the db process dead error message appears. Is the
> anyway to extend the time out setting to longer time so that this
> problem could be minimise?
> Thanks a million.
>|||The dbprocess dead error indicates a terminated connection rather than a
timeout. The application needs to be smart enough to attempt to reconnect
following the error.
--
Hope this helps.
Dan Guzman
SQL Server MVP
<masterwee@.gmail.com> wrote in message
news:1162278624.684826.264940@.m73g2000cwd.googlegroups.com...
> Hi,
> I really need some help here. I have a few sql clients that connects to
> my sql server through wireless connection. Sometimes, these wireless
> connections link is down for a few seconds. When user try to continue
> to run some query, the db process dead error message appears. Is the
> anyway to extend the time out setting to longer time so that this
> problem could be minimise?
> Thanks a million.
>|||I have similar problems on some remote sites. Some are running the client
over ISDN which naturally timesout and should pick up the line again when
there is activity. But when the user generates some activity we get the db
process dead message. We migrated these sites from Sybase which never had
these issues and seemed more robust in these situations.
Is there any config options we can use on the client or server to make the
connections less fickle?
Is there any updated client that might be more reliable?
We are using SQL Server 2000 Sp4 but the client is the one on the original
SQl Server 2000 CD.
Thanks,
"Dan Guzman" wrote:
> The dbprocess dead error indicates a terminated connection rather than a
> timeout. The application needs to be smart enough to attempt to reconnect
> following the error.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> <masterwee@.gmail.com> wrote in message
> news:1162278624.684826.264940@.m73g2000cwd.googlegroups.com...
> > Hi,
> >
> > I really need some help here. I have a few sql clients that connects to
> > my sql server through wireless connection. Sometimes, these wireless
> > connections link is down for a few seconds. When user try to continue
> > to run some query, the db process dead error message appears. Is the
> > anyway to extend the time out setting to longer time so that this
> > problem could be minimise?
> >
> > Thanks a million.
> >
>|||Hi Marty
Unless you have the SQL Server tools on the client PC then there is no point
in using it on the client. You should make sure that a recent version of MDAC
is on there, although I don't think this will cure the issue as the server
can not reach the client and it can not instigate the ISDN connection.
As Dan has stated you will need to handle the error and reconnect the client
if you get this error.
Has the client application changed from powerbuilder?
John
"Marty" wrote:
> I have similar problems on some remote sites. Some are running the client
> over ISDN which naturally timesout and should pick up the line again when
> there is activity. But when the user generates some activity we get the db
> process dead message. We migrated these sites from Sybase which never had
> these issues and seemed more robust in these situations.
> Is there any config options we can use on the client or server to make the
> connections less fickle?
> Is there any updated client that might be more reliable?
> We are using SQL Server 2000 Sp4 but the client is the one on the original
> SQl Server 2000 CD.
> Thanks,
>
> "Dan Guzman" wrote:
> > The dbprocess dead error indicates a terminated connection rather than a
> > timeout. The application needs to be smart enough to attempt to reconnect
> > following the error.
> >
> > --
> > Hope this helps.
> >
> > Dan Guzman
> > SQL Server MVP
> >
> > <masterwee@.gmail.com> wrote in message
> > news:1162278624.684826.264940@.m73g2000cwd.googlegroups.com...
> > > Hi,
> > >
> > > I really need some help here. I have a few sql clients that connects to
> > > my sql server through wireless connection. Sometimes, these wireless
> > > connections link is down for a few seconds. When user try to continue
> > > to run some query, the db process dead error message appears. Is the
> > > anyway to extend the time out setting to longer time so that this
> > > problem could be minimise?
> > >
> > > Thanks a million.
> > >
> >|||John,
When any activity happens on the client, it wakes up the ISDN connection and
should carry on where it left off in the application, but it looks like the
Client does not re-connect to the server correctly.
I'm not sure which SQL Server tools you refer to?
As for MDAC, it will be the one on the CD, should there be a later version?
The application is written in C++ not Powerbuilder. It is the database which
has been migrated to SQL Server from Sybase, and the old Sybase Open Client
did not report these errors on the same ISDN line.
Thanks,
M
"John Bell" wrote:
> Hi Marty
> Unless you have the SQL Server tools on the client PC then there is no point
> in using it on the client. You should make sure that a recent version of MDAC
> is on there, although I don't think this will cure the issue as the server
> can not reach the client and it can not instigate the ISDN connection.
> As Dan has stated you will need to handle the error and reconnect the client
> if you get this error.
> Has the client application changed from powerbuilder?
> John
> "Marty" wrote:
> > I have similar problems on some remote sites. Some are running the client
> > over ISDN which naturally timesout and should pick up the line again when
> > there is activity. But when the user generates some activity we get the db
> > process dead message. We migrated these sites from Sybase which never had
> > these issues and seemed more robust in these situations.
> >
> > Is there any config options we can use on the client or server to make the
> > connections less fickle?
> > Is there any updated client that might be more reliable?
> > We are using SQL Server 2000 Sp4 but the client is the one on the original
> > SQl Server 2000 CD.
> >
> > Thanks,
> >
> >
> >
> > "Dan Guzman" wrote:
> >
> > > The dbprocess dead error indicates a terminated connection rather than a
> > > timeout. The application needs to be smart enough to attempt to reconnect
> > > following the error.
> > >
> > > --
> > > Hope this helps.
> > >
> > > Dan Guzman
> > > SQL Server MVP
> > >
> > > <masterwee@.gmail.com> wrote in message
> > > news:1162278624.684826.264940@.m73g2000cwd.googlegroups.com...
> > > > Hi,
> > > >
> > > > I really need some help here. I have a few sql clients that connects to
> > > > my sql server through wireless connection. Sometimes, these wireless
> > > > connections link is down for a few seconds. When user try to continue
> > > > to run some query, the db process dead error message appears. Is the
> > > > anyway to extend the time out setting to longer time so that this
> > > > problem could be minimise?
> > > >
> > > > Thanks a million.
> > > >
> > >|||Hi Marty
Use the MDAC checker from
http://msdn.microsoft.com/data/ref/mdac/downloads/. MDAC can be updated
through other products such as XP SP1, so you may not be on the same version
at all sites. You will need to change the client application so that if the
error is detected the connection is closed and re-open it. I don't know if
the Open Client has the intellegence to silently reconnect or if it was
sending a keep alive.
John
"Marty" wrote:
> John,
> When any activity happens on the client, it wakes up the ISDN connection and
> should carry on where it left off in the application, but it looks like the
> Client does not re-connect to the server correctly.
> I'm not sure which SQL Server tools you refer to?
> As for MDAC, it will be the one on the CD, should there be a later version?
> The application is written in C++ not Powerbuilder. It is the database which
> has been migrated to SQL Server from Sybase, and the old Sybase Open Client
> did not report these errors on the same ISDN line.
> Thanks,
> M
>
> "John Bell" wrote:
> > Hi Marty
> >
> > Unless you have the SQL Server tools on the client PC then there is no point
> > in using it on the client. You should make sure that a recent version of MDAC
> > is on there, although I don't think this will cure the issue as the server
> > can not reach the client and it can not instigate the ISDN connection.
> >
> > As Dan has stated you will need to handle the error and reconnect the client
> > if you get this error.
> >
> > Has the client application changed from powerbuilder?
> >
> > John
> >
> > "Marty" wrote:
> >
> > > I have similar problems on some remote sites. Some are running the client
> > > over ISDN which naturally timesout and should pick up the line again when
> > > there is activity. But when the user generates some activity we get the db
> > > process dead message. We migrated these sites from Sybase which never had
> > > these issues and seemed more robust in these situations.
> > >
> > > Is there any config options we can use on the client or server to make the
> > > connections less fickle?
> > > Is there any updated client that might be more reliable?
> > > We are using SQL Server 2000 Sp4 but the client is the one on the original
> > > SQl Server 2000 CD.
> > >
> > > Thanks,
> > >
> > >
> > >
> > > "Dan Guzman" wrote:
> > >
> > > > The dbprocess dead error indicates a terminated connection rather than a
> > > > timeout. The application needs to be smart enough to attempt to reconnect
> > > > following the error.
> > > >
> > > > --
> > > > Hope this helps.
> > > >
> > > > Dan Guzman
> > > > SQL Server MVP
> > > >
> > > > <masterwee@.gmail.com> wrote in message
> > > > news:1162278624.684826.264940@.m73g2000cwd.googlegroups.com...
> > > > > Hi,
> > > > >
> > > > > I really need some help here. I have a few sql clients that connects to
> > > > > my sql server through wireless connection. Sometimes, these wireless
> > > > > connections link is down for a few seconds. When user try to continue
> > > > > to run some query, the db process dead error message appears. Is the
> > > > > anyway to extend the time out setting to longer time so that this
> > > > > problem could be minimise?
> > > > >
> > > > > Thanks a million.
> > > > >
> > > >

Expressions in For Loop Container

Hi,
I am having problem when setting for-each container's EvalExpression as a variable comparison.

I have set this in expression editor
@.[User::Syn] == 1

Editor says that it couldnt convert from System.Bool to System.String.

If I put it in quote, then for-each container says that it needs Bool, not String.

Please help me with this,
Thanks
@.[User::Syn] == "1"|||Syn is of Int32 datatype.
And now it says

Expression cannot be evaluated.

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%u00ae+Visual+Studio%u00ae+2005&ProdVer=8.0.50727.42&EvtSrc=Microsoft.DataTransformationServices.Controls.TaskUIFramework.TaskUIFrameworkSR&EvtID=FailToEvaluateExpression&LinkId=20476

The data types "DT_I4" and "DT_WSTR" are incompatible for binary operator "==". The operand types could not be implicitly cast into compatible types for the operation. To perform this operation, one or both operands need to be explicitly cast with a cast operator.

Attempt to set the result type of binary operation "@.[User::SyncStatus] == "0"" failed with error code 0xC0047080.

(Microsoft.DataTransformationServices.Controls)|||actually, EvalExpression property is string and expression editor must end up with some string value and something == something is basically a boolean.|||So is it User::Syn or User::SyncStatus? If SyncStatus is a DT_I4, then this should work:

@.[User::SyncStatus] == 0

It works for me.|||

Fahad349 wrote:

actually, EvalExpression property is string and expression editor must end up with some string value andsomething == something is basically a boolean.

EvalExpression "must evaluate to a Boolean"|||

Fahad349 wrote:

actually, EvalExpression property is string and expression editor must end up with some string value andsomething == something is basically a boolean.

Why aren't you using the EvalExpression in the editor, not the expression property?

If you are editing the property expressions, then this is what you'd want:

"@.[User::SyncStatus] == 0"

Expression for Color property

I keep getting a message when setting the expression for the color property.
When I exit the expression builder an error message is displayed showing the
expression and "not a valid color". I have tried numerous IIF but cannot get
past the error.
IIF( Fields!ACCOUNT_STATUS.Value="LOCKED","Red","Green")
What am I missing? Thanks in advance...Make sure you put a = sign before IIF
so the expression should be
=IIF( Fields!ACCOUNT_STATUS.Value="LOCKED","Red","Green")
Hope this helps
RP
"Stanley Hammer" wrote:
> I keep getting a message when setting the expression for the color property.
> When I exit the expression builder an error message is displayed showing the
> expression and "not a valid color". I have tried numerous IIF but cannot get
> past the error.
> IIF( Fields!ACCOUNT_STATUS.Value="LOCKED","Red","Green")
> What am I missing? Thanks in advance...|||Thanks, that worked great.
"RP" wrote:
> Make sure you put a = sign before IIF
> so the expression should be
> =IIF( Fields!ACCOUNT_STATUS.Value="LOCKED","Red","Green")
> Hope this helps
> RP
> "Stanley Hammer" wrote:
> > I keep getting a message when setting the expression for the color property.
> > When I exit the expression builder an error message is displayed showing the
> > expression and "not a valid color". I have tried numerous IIF but cannot get
> > past the error.
> >
> > IIF( Fields!ACCOUNT_STATUS.Value="LOCKED","Red","Green")
> >
> > What am I missing? Thanks in advance...