do not have permission error message

I have been trying to run a script that modifies objects in a SQL Server 2005 database. I am trying to drop an index but I am told the index does not exist or I do not have the correct permissions. An example of one of the commands in the script that I am trying to execute are as follows.

command:
DROP INDEX spices.ADAPTER_MESSAGE.ADAPTER_MESSAGE_SET;

response:
Msg 3701, Level 11, State 6, Line 1
Cannot drop the index 'spices.ADAPTER_MESSAGE.ADAPTER_MESSAGE_SET', because it does not exist or you do not have permission.

The index does exist in the table so the problem must be related to permissions. I am the one who created the database so I am the dbo. I should have permission to do anything in the database, right? So why am I getting this error when my script runs?

thanks,
shimo

The dbo should be able to drop the index.

Is it possible that you are not running as the dbo? Maybe an application role has been set or something like that.

One way to check is

select user_name() to determine your user context.

Another possiblility is that the spices table is not in dbo or your default schema.

Try using the two part name schema.spices.ADAPTER_MESSAGE.ADAPTER_MESSAGE_SET

HTH,

-Steven Gott

S/DET

SQL Server

|||

Is this a SQL x64 bit edition?

We have had similar issue and reported to MS Connect site.

sql

do i need to deny everything i don't use ?

hi again
i have an account with its password
with specific permissions,
i have to deny, then, the access
to the rest of the objects ?
i.e. systems stored proc, tables , etc ?
thanks
atte,
Hernn Castelo
SGA - UTN - FRBA
Depends what you want.
The user will only have access to those objects it is granted so there is no
need to deny.
But if the user is then added to a role which has other permissions (or they
are given to public) it will gain them.
If this is not what you want then you should deny permissions as well.
I usually only deny dbwriter to read only accounts and leave the rest to
gain from granted permissions
"Hernán Castelo" wrote:

> hi again
> i have an account with its password
> with specific permissions,
> i have to deny, then, the access
> to the rest of the objects ?
> i.e. systems stored proc, tables , etc ?
> thanks
>
> --
> atte,
> Hernán Castelo
> SGA - UTN - FRBA
>
>
|||i'm asking because
i entered with a restricted account
and was able to exec SP_HELPTEXT
and i don't wish that
denying dbwriter sounds good,
how can i disable these type of sp's ?
atte,
Hernn Castelo
SGA - UTN - FRBA
"Nigel Rivett" <sqlnr@.hotmail.com> escribi en el mensaje
news:FA87EBFA-AE01-4BDD-8869-E62687DB27FB@.microsoft.com...
> Depends what you want.
> The user will only have access to those objects it is granted so there is
no
> need to deny.
> But if the user is then added to a role which has other permissions (or
they[vbcol=seagreen]
> are given to public) it will gain them.
> If this is not what you want then you should deny permissions as well.
> I usually only deny dbwriter to read only accounts and leave the rest to
> gain from granted permissions
> "Hernn Castelo" wrote:
|||Everyone can see the source code, I'm afraid. Closest you can come is creating the procedures using
the WITH ENCRYPTION option (note however that there exists tools to decrypt...).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Hernn Castelo" <bajopalabra@.hotmail.com> wrote in message
news:OO0nNnM0EHA.3416@.TK2MSFTNGP09.phx.gbl...
> i'm asking because
> i entered with a restricted account
> and was able to exec SP_HELPTEXT
> and i don't wish that
> denying dbwriter sounds good,
> how can i disable these type of sp's ?
>
> --
> atte,
> Hernn Castelo
> SGA - UTN - FRBA
> "Nigel Rivett" <sqlnr@.hotmail.com> escribi en el mensaje
> news:FA87EBFA-AE01-4BDD-8869-E62687DB27FB@.microsoft.com...
> no
> they
>

do i need to deny everything i don't use ?

hi again
i have an account with its password
with specific permissions,
i have to deny, then, the access
to the rest of the objects ?
i.e. systems stored proc, tables , etc ?
thanks
atte,
Hernn Castelo
SGA - UTN - FRBADepends what you want.
The user will only have access to those objects it is granted so there is no
need to deny.
But if the user is then added to a role which has other permissions (or they
are given to public) it will gain them.
If this is not what you want then you should deny permissions as well.
I usually only deny dbwriter to read only accounts and leave the rest to
gain from granted permissions
"Hernán Castelo" wrote:

> hi again
> i have an account with its password
> with specific permissions,
> i have to deny, then, the access
> to the rest of the objects ?
> i.e. systems stored proc, tables , etc ?
> thanks
>
> --
> atte,
> Hernán Castelo
> SGA - UTN - FRBA
>
>|||i'm asking because
i entered with a restricted account
and was able to exec SP_HELPTEXT
and i don't wish that
denying dbwriter sounds good,
how can i disable these type of sp's ?
atte,
Hernn Castelo
SGA - UTN - FRBA
"Nigel Rivett" <sqlnr@.hotmail.com> escribi en el mensaje
news:FA87EBFA-AE01-4BDD-8869-E62687DB27FB@.microsoft.com...
> Depends what you want.
> The user will only have access to those objects it is granted so there is
no
> need to deny.
> But if the user is then added to a role which has other permissions (or
they[vbcol=seagreen]
> are given to public) it will gain them.
> If this is not what you want then you should deny permissions as well.
> I usually only deny dbwriter to read only accounts and leave the rest to
> gain from granted permissions
> "Hernn Castelo" wrote:
>|||Everyone can see the source code, I'm afraid. Closest you can come is creati
ng the procedures using
the WITH ENCRYPTION option (note however that there exists tools to decrypt.
.).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Hernn Castelo" <bajopalabra@.hotmail.com> wrote in message
news:OO0nNnM0EHA.3416@.TK2MSFTNGP09.phx.gbl...
> i'm asking because
> i entered with a restricted account
> and was able to exec SP_HELPTEXT
> and i don't wish that
> denying dbwriter sounds good,
> how can i disable these type of sp's ?
>
> --
> atte,
> Hernn Castelo
> SGA - UTN - FRBA
> "Nigel Rivett" <sqlnr@.hotmail.com> escribi en el mensaje
> news:FA87EBFA-AE01-4BDD-8869-E62687DB27FB@.microsoft.com...
> no
> they
>

do i need to deny everything i don't use ?

hi again
i have an account with its password
with specific permissions,
i have to deny, then, the access
to the rest of the objects ?
i.e. systems stored proc, tables , etc ?
thanks
--
atte,
Hernán Castelo
SGA - UTN - FRBADepends what you want.
The user will only have access to those objects it is granted so there is no
need to deny.
But if the user is then added to a role which has other permissions (or they
are given to public) it will gain them.
If this is not what you want then you should deny permissions as well.
I usually only deny dbwriter to read only accounts and leave the rest to
gain from granted permissions
"Hernán Castelo" wrote:
> hi again
> i have an account with its password
> with specific permissions,
> i have to deny, then, the access
> to the rest of the objects ?
> i.e. systems stored proc, tables , etc ?
> thanks
>
> --
> atte,
> Hernán Castelo
> SGA - UTN - FRBA
>
>|||i'm asking because
i entered with a restricted account
and was able to exec SP_HELPTEXT
and i don't wish that
denying dbwriter sounds good,
how can i disable these type of sp's ?
atte,
Hernán Castelo
SGA - UTN - FRBA
"Nigel Rivett" <sqlnr@.hotmail.com> escribió en el mensaje
news:FA87EBFA-AE01-4BDD-8869-E62687DB27FB@.microsoft.com...
> Depends what you want.
> The user will only have access to those objects it is granted so there is
no
> need to deny.
> But if the user is then added to a role which has other permissions (or
they
> are given to public) it will gain them.
> If this is not what you want then you should deny permissions as well.
> I usually only deny dbwriter to read only accounts and leave the rest to
> gain from granted permissions
> "Hernán Castelo" wrote:
> > hi again
> > i have an account with its password
> > with specific permissions,
> > i have to deny, then, the access
> > to the rest of the objects ?
> > i.e. systems stored proc, tables , etc ?
> >
> > thanks
> >
> >
> > --
> > atte,
> > Hernán Castelo
> > SGA - UTN - FRBA
> >
> >
> >|||Everyone can see the source code, I'm afraid. Closest you can come is creating the procedures using
the WITH ENCRYPTION option (note however that there exists tools to decrypt...).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Hernán Castelo" <bajopalabra@.hotmail.com> wrote in message
news:OO0nNnM0EHA.3416@.TK2MSFTNGP09.phx.gbl...
> i'm asking because
> i entered with a restricted account
> and was able to exec SP_HELPTEXT
> and i don't wish that
> denying dbwriter sounds good,
> how can i disable these type of sp's ?
>
> --
> atte,
> Hernán Castelo
> SGA - UTN - FRBA
> "Nigel Rivett" <sqlnr@.hotmail.com> escribió en el mensaje
> news:FA87EBFA-AE01-4BDD-8869-E62687DB27FB@.microsoft.com...
> > Depends what you want.
> > The user will only have access to those objects it is granted so there is
> no
> > need to deny.
> > But if the user is then added to a role which has other permissions (or
> they
> > are given to public) it will gain them.
> > If this is not what you want then you should deny permissions as well.
> >
> > I usually only deny dbwriter to read only accounts and leave the rest to
> > gain from granted permissions
> >
> > "Hernán Castelo" wrote:
> >
> > > hi again
> > > i have an account with its password
> > > with specific permissions,
> > > i have to deny, then, the access
> > > to the rest of the objects ?
> > > i.e. systems stored proc, tables , etc ?
> > >
> > > thanks
> > >
> > >
> > > --
> > > atte,
> > > Hernán Castelo
> > > SGA - UTN - FRBA
> > >
> > >
> > >
>

DMO & SQL 2005

Will SQL 2005 still have SQLDMO?
Will the objects have the same name as with SQL7/SQL2000?
dirk.I believe it will be supported for backward compatibility but the new
technology is known as SMO.
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"Dirk" <dirk@.nospam_to_remove_ofcourse.woodstone.nu> wrote in message
news:elhsDVSZEHA.3664@.TK2MSFTNGP12.phx.gbl...
Will SQL 2005 still have SQLDMO?
Will the objects have the same name as with SQL7/SQL2000?
dirk.|||Yes, there will be SQLDMO 9 shipping in SQL Server 2005. It will work at
the 8.0 level against a SQL Server 2005 system, so no new features will be
exposed, but it will continue to function.
Richard Waymire, MCSE, MCDBA
This posting is provided AS IS with no warranties, and confers no rights.
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:%23Z1PiZSZEHA.3112@.TK2MSFTNGP09.phx.gbl...
>I believe it will be supported for backward compatibility but the new
> technology is known as SMO.
> --
> Tom
> ---
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com/sql
>
> "Dirk" <dirk@.nospam_to_remove_ofcourse.woodstone.nu> wrote in message
> news:elhsDVSZEHA.3664@.TK2MSFTNGP12.phx.gbl...
> Will SQL 2005 still have SQLDMO?
> Will the objects have the same name as with SQL7/SQL2000?
>
> dirk.
>|||So it will use the same objects/syntax as those for SQL2000 then?
dirk;
"Richard Waymire [MSFT]" <rwaymi@.online.microsoft.com> wrote in message
news:uV1sFoSZEHA.3144@.TK2MSFTNGP12.phx.gbl...
> Yes, there will be SQLDMO 9 shipping in SQL Server 2005. It will work at
> the 8.0 level against a SQL Server 2005 system, so no new features will be
> exposed, but it will continue to function.
> --
> Richard Waymire, MCSE, MCDBA
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:%23Z1PiZSZEHA.3112@.TK2MSFTNGP09.phx.gbl...
>|||Yes.
Richard Waymire, MCSE, MCDBA
This posting is provided "AS IS" with no warranties, and confers no rights.
"Dirk" <dirk@.nospam_to_remove_ofcourse.woodstone.nu> wrote in message
news:eWbpZpTZEHA.2444@.tk2msftngp13.phx.gbl...
> So it will use the same objects/syntax as those for SQL2000 then?
>
> dirk;
> "Richard Waymire [MSFT]" <rwaymi@.online.microsoft.com> wrote in messag
e
> news:uV1sFoSZEHA.3144@.TK2MSFTNGP12.phx.gbl...
> rights.
>
>|||Great thanks.
"Richard Waymire [MSFT]" <rwaymi@.online.microsoft.com> wrote in message
news:eNDWDJUZEHA.1048@.tk2msftngp13.phx.gbl...
> Yes.
> --
> Richard Waymire, MCSE, MCDBA
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Dirk" <dirk@.nospam_to_remove_ofcourse.woodstone.nu> wrote in message
> news:eWbpZpTZEHA.2444@.tk2msftngp13.phx.gbl...
at[vbcol=seagreen]
>

DMO & SQL 2005

Will SQL 2005 still have SQLDMO?
Will the objects have the same name as with SQL7/SQL2000?
dirk.I believe it will be supported for backward compatibility but the new
technology is known as SMO.
--
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"Dirk" <dirk@.nospam_to_remove_ofcourse.woodstone.nu> wrote in message
news:elhsDVSZEHA.3664@.TK2MSFTNGP12.phx.gbl...
Will SQL 2005 still have SQLDMO?
Will the objects have the same name as with SQL7/SQL2000?
dirk.|||Yes, there will be SQLDMO 9 shipping in SQL Server 2005. It will work at
the 8.0 level against a SQL Server 2005 system, so no new features will be
exposed, but it will continue to function.
--
Richard Waymire, MCSE, MCDBA
This posting is provided ?AS IS? with no warranties, and confers no rights.
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:%23Z1PiZSZEHA.3112@.TK2MSFTNGP09.phx.gbl...
>I believe it will be supported for backward compatibility but the new
> technology is known as SMO.
> --
> Tom
> ---
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com/sql
>
> "Dirk" <dirk@.nospam_to_remove_ofcourse.woodstone.nu> wrote in message
> news:elhsDVSZEHA.3664@.TK2MSFTNGP12.phx.gbl...
> Will SQL 2005 still have SQLDMO?
> Will the objects have the same name as with SQL7/SQL2000?
>
> dirk.
>|||So it will use the same objects/syntax as those for SQL2000 then?
dirk;
"Richard Waymire [MSFT]" <rwaymi@.online.microsoft.com> wrote in message
news:uV1sFoSZEHA.3144@.TK2MSFTNGP12.phx.gbl...
> Yes, there will be SQLDMO 9 shipping in SQL Server 2005. It will work at
> the 8.0 level against a SQL Server 2005 system, so no new features will be
> exposed, but it will continue to function.
> --
> Richard Waymire, MCSE, MCDBA
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:%23Z1PiZSZEHA.3112@.TK2MSFTNGP09.phx.gbl...
> >I believe it will be supported for backward compatibility but the new
> > technology is known as SMO.
> >
> > --
> > Tom
> >
> > ---
> > Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> > SQL Server MVP
> > Columnist, SQL Server Professional
> > Toronto, ON Canada
> > www.pinnaclepublishing.com/sql
> >
> >
> > "Dirk" <dirk@.nospam_to_remove_ofcourse.woodstone.nu> wrote in message
> > news:elhsDVSZEHA.3664@.TK2MSFTNGP12.phx.gbl...
> > Will SQL 2005 still have SQLDMO?
> > Will the objects have the same name as with SQL7/SQL2000?
> >
> >
> >
> > dirk.
> >
> >
>|||Yes.
--
Richard Waymire, MCSE, MCDBA
This posting is provided "AS IS" with no warranties, and confers no rights.
"Dirk" <dirk@.nospam_to_remove_ofcourse.woodstone.nu> wrote in message
news:eWbpZpTZEHA.2444@.tk2msftngp13.phx.gbl...
> So it will use the same objects/syntax as those for SQL2000 then?
>
> dirk;
> "Richard Waymire [MSFT]" <rwaymi@.online.microsoft.com> wrote in message
> news:uV1sFoSZEHA.3144@.TK2MSFTNGP12.phx.gbl...
>> Yes, there will be SQLDMO 9 shipping in SQL Server 2005. It will work at
>> the 8.0 level against a SQL Server 2005 system, so no new features will
>> be
>> exposed, but it will continue to function.
>> --
>> Richard Waymire, MCSE, MCDBA
>> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:%23Z1PiZSZEHA.3112@.TK2MSFTNGP09.phx.gbl...
>> >I believe it will be supported for backward compatibility but the new
>> > technology is known as SMO.
>> >
>> > --
>> > Tom
>> >
>> > ---
>> > Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> > SQL Server MVP
>> > Columnist, SQL Server Professional
>> > Toronto, ON Canada
>> > www.pinnaclepublishing.com/sql
>> >
>> >
>> > "Dirk" <dirk@.nospam_to_remove_ofcourse.woodstone.nu> wrote in message
>> > news:elhsDVSZEHA.3664@.TK2MSFTNGP12.phx.gbl...
>> > Will SQL 2005 still have SQLDMO?
>> > Will the objects have the same name as with SQL7/SQL2000?
>> >
>> >
>> >
>> > dirk.
>> >
>> >
>>
>
>|||Great thanks.
"Richard Waymire [MSFT]" <rwaymi@.online.microsoft.com> wrote in message
news:eNDWDJUZEHA.1048@.tk2msftngp13.phx.gbl...
> Yes.
> --
> Richard Waymire, MCSE, MCDBA
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Dirk" <dirk@.nospam_to_remove_ofcourse.woodstone.nu> wrote in message
> news:eWbpZpTZEHA.2444@.tk2msftngp13.phx.gbl...
> > So it will use the same objects/syntax as those for SQL2000 then?
> >
> >
> > dirk;
> >
> > "Richard Waymire [MSFT]" <rwaymi@.online.microsoft.com> wrote in message
> > news:uV1sFoSZEHA.3144@.TK2MSFTNGP12.phx.gbl...
> >> Yes, there will be SQLDMO 9 shipping in SQL Server 2005. It will work
at
> >> the 8.0 level against a SQL Server 2005 system, so no new features will
> >> be
> >> exposed, but it will continue to function.
> >>
> >> --
> >> Richard Waymire, MCSE, MCDBA
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> >> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> >> news:%23Z1PiZSZEHA.3112@.TK2MSFTNGP09.phx.gbl...
> >> >I believe it will be supported for backward compatibility but the new
> >> > technology is known as SMO.
> >> >
> >> > --
> >> > Tom
> >> >
> >> > ---
> >> > Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> >> > SQL Server MVP
> >> > Columnist, SQL Server Professional
> >> > Toronto, ON Canada
> >> > www.pinnaclepublishing.com/sql
> >> >
> >> >
> >> > "Dirk" <dirk@.nospam_to_remove_ofcourse.woodstone.nu> wrote in message
> >> > news:elhsDVSZEHA.3664@.TK2MSFTNGP12.phx.gbl...
> >> > Will SQL 2005 still have SQLDMO?
> >> > Will the objects have the same name as with SQL7/SQL2000?
> >> >
> >> >
> >> >
> >> > dirk.
> >> >
> >> >
> >>
> >>
> >
> >
> >
>

DMO & SQL 2005

Will SQL 2005 still have SQLDMO?
Will the objects have the same name as with SQL7/SQL2000?
dirk.
I believe it will be supported for backward compatibility but the new
technology is known as SMO.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"Dirk" <dirk@.nospam_to_remove_ofcourse.woodstone.nu> wrote in message
news:elhsDVSZEHA.3664@.TK2MSFTNGP12.phx.gbl...
Will SQL 2005 still have SQLDMO?
Will the objects have the same name as with SQL7/SQL2000?
dirk.
|||Yes, there will be SQLDMO 9 shipping in SQL Server 2005. It will work at
the 8.0 level against a SQL Server 2005 system, so no new features will be
exposed, but it will continue to function.
Richard Waymire, MCSE, MCDBA
This posting is provided AS IS with no warranties, and confers no rights.
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:%23Z1PiZSZEHA.3112@.TK2MSFTNGP09.phx.gbl...
>I believe it will be supported for backward compatibility but the new
> technology is known as SMO.
> --
> Tom
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com/sql
>
> "Dirk" <dirk@.nospam_to_remove_ofcourse.woodstone.nu> wrote in message
> news:elhsDVSZEHA.3664@.TK2MSFTNGP12.phx.gbl...
> Will SQL 2005 still have SQLDMO?
> Will the objects have the same name as with SQL7/SQL2000?
>
> dirk.
>
|||So it will use the same objects/syntax as those for SQL2000 then?
dirk;
"Richard Waymire [MSFT]" <rwaymi@.online.microsoft.com> wrote in message
news:uV1sFoSZEHA.3144@.TK2MSFTNGP12.phx.gbl...
> Yes, there will be SQLDMO 9 shipping in SQL Server 2005. It will work at
> the 8.0 level against a SQL Server 2005 system, so no new features will be
> exposed, but it will continue to function.
> --
> Richard Waymire, MCSE, MCDBA
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:%23Z1PiZSZEHA.3112@.TK2MSFTNGP09.phx.gbl...
>
|||Yes.
Richard Waymire, MCSE, MCDBA
This posting is provided "AS IS" with no warranties, and confers no rights.
"Dirk" <dirk@.nospam_to_remove_ofcourse.woodstone.nu> wrote in message
news:eWbpZpTZEHA.2444@.tk2msftngp13.phx.gbl...
> So it will use the same objects/syntax as those for SQL2000 then?
>
> dirk;
> "Richard Waymire [MSFT]" <rwaymi@.online.microsoft.com> wrote in message
> news:uV1sFoSZEHA.3144@.TK2MSFTNGP12.phx.gbl...
> rights.
>
>
|||Great thanks.
"Richard Waymire [MSFT]" <rwaymi@.online.microsoft.com> wrote in message
news:eNDWDJUZEHA.1048@.tk2msftngp13.phx.gbl...
> Yes.
> --
> Richard Waymire, MCSE, MCDBA
> This posting is provided "AS IS" with no warranties, and confers no
rights.[vbcol=seagreen]
> "Dirk" <dirk@.nospam_to_remove_ofcourse.woodstone.nu> wrote in message
> news:eWbpZpTZEHA.2444@.tk2msftngp13.phx.gbl...
at
>