Showing posts with label saying. Show all posts
Showing posts with label saying. Show all posts

Tuesday, March 27, 2012

cannot edit text cell

I am trying to edit a long text cell in Enterprise Manager but when I select
"<long text>" and try to delete it, I get an error saying "cannot edit this
cell".

Could anyone tell me how to edit this cell?

Thanks, AmandaHi

When your text column has more than 900 characters it will not allow you to
enter it via EM.

You can use Query Analyser (which is usually easier and safer IMO) to issue
an update statement, or for more complicated changes look up UPDATETEXT in
books online.

John

"Amanda H" <amanda2@.southwind.org> wrote in message
news:K58Pd.1784$VI1.215392@.twister.southeast.rr.co m...
>I am trying to edit a long text cell in Enterprise Manager but when I
>select
> "<long text>" and try to delete it, I get an error saying "cannot edit
> this
> cell".
> Could anyone tell me how to edit this cell?
> Thanks, Amanda|||"Amanda H" <amanda2@.southwind.org> wrote in message
news:K58Pd.1784$VI1.215392@.twister.southeast.rr.co m...
>I am trying to edit a long text cell in Enterprise Manager but when I
>select
> "<long text>" and try to delete it, I get an error saying "cannot edit
> this
> cell".
> Could anyone tell me how to edit this cell?
> Thanks, Amanda

Use an UPDATE statement in Query Analyzer is probably the best thing to do -
EM isn't really a data manipulation or development tool, and it has a number
of 'features'.

http://www.aspfaq.com/show.asp?id=2455

Simonsql

Friday, February 10, 2012

Cannot connect to a named instance of SQL 2000 or 2005

Hi,

I am struggling connection to a named instance of SQL 2000 (SP4) from another machine but without any success. I get an error message saying that the server does not exist or access is denied.

The security configuration in this named instance is the same as the default instance (also 2000) and the remote machine can connect to it successfully.

I also configured the aliases in Client Network Utility in the client machine and set the server (machine) name and the port number used by the instance - but no help.

I use osql and Query Analyzer to connect to it, but I cannot connect by any of them.

Connecting locally, in the machine where the instance is installed, is successful.

The same behaviour appears when I try to connect to another instance on the machine which is 2005.

Something with the named instance is problematic.

Any help?

Hi,

What OSQL string did you use to connect to SQL Server. If you have a named instance you probably have another port number assigned to the additional service to listen to the network. If so, you have to prvide the port number while connecting to the server.

OSQL -SServername,Portnumber <otherparams>

HTH, Jens Suessmeyer.

|||

Thanks Jens.

I think I found the problem. it is all about Win XP SP2 firewall clocking TCP/IP connections to SQL Server.

All the asweres are in Microsfot KB articles:

841394 (http://support.microsoft.com/?scid=kb;en-us;841394&spid=2855&sid=332)

841252 (http://support.microsoft.com/kb/841252/)

841251 (http://support.microsoft.com/kb/841251/)

and the other relevant artickles referred there.