How to Set Thousand Separator?

Hi,
This topic has been raised a few time in the newsgroup and the solution
has been to set the 'Langauge' property of the report.
In my report, I can't find the Language propertie, neither in the
properties from he menu in VS nor in the Property Grid.
Can anyone point me in the right direction?
Thanks,
DomDom, in the properties pane (press F4 if you can't see it) there is a
drop-down list at the top where you can select objects. Use this and
choose 'Report' and in the 'Misc' properties section you'll see
Language.
If you want to default new reports to your Windows Language, you can do
Tools|Options|Environment|General|International Settings and change it
to 'Same as Office'. This affects anything you do in VS/VB though.
Chris
DominicB wrote:
> Hi,
> This topic has been raised a few time in the newsgroup and the
> solution has been to set the 'Langauge' property of the report.
> In my report, I can't find the Language propertie, neither in the
> properties from he menu in VS nor in the Property Grid.
> Can anyone point me in the right direction?
> Thanks,
> Dom|||Ace, Chris!
Cheers,
Dom
Chris McGuigan wrote:
> Dom, in the properties pane (press F4 if you can't see it) there is a
> drop-down list at the top where you can select objects. Use this and
> choose 'Report' and in the 'Misc' properties section you'll see
> Language.
> If you want to default new reports to your Windows Language, you can do
> Tools|Options|Environment|General|International Settings and change it
> to 'Same as Office'. This affects anything you do in VS/VB though.
> Chris
> DominicB wrote:
> > Hi,
> > This topic has been raised a few time in the newsgroup and the
> > solution has been to set the 'Langauge' property of the report.
> >
> > In my report, I can't find the Language propertie, neither in the
> > properties from he menu in VS nor in the Property Grid.
> >
> > Can anyone point me in the right direction?
> >
> > Thanks,
> > Dom

How to set Tab as column separator in SQL*Plus?

Any advice or workarounds, greatly appreciated.
Cheers,
PeiOriginally posted by peisiong
Any advice or workarounds, greatly appreciated.

Cheers,

Pei
You could do this:

SQL> column tab new_value tab
SQL> select chr(9) tab from dual;

T
-


SQL> set colsep "&tab"|||[QUOTE][SIZE=1]Originally posted by andrewst
Thanks Andrew!!!|||Hi

I have done what you have suggested and the spooled file looks ok when I open it in EXCEL.

But when I open it in a text editor, there seems to be spaces (lots of them) in place of tab.

Any idea why?

Cheers,

Pei Siong|||Originally posted by peisiong
Hi

I have done what you have suggested and the spooled file looks ok when I open it in EXCEL.

But when I open it in a text editor, there seems to be spaces (lots of them) in place of tab.

Any idea why?

Cheers,

Pei Siong
There are spaces, as well as the delimiting TABs, because of the way SQL Plus formats the data WITHIN the columns, e.g.:

____DEPTNO|DNAME_________|LOC_________
----|-----|----
________10|ACCOUNTING____|NEW_YORK____
________20|RESEARCH______|DALLAS______
________30|SALES_________|CHICAGO_____
________40|OPERATIONS____|BOSTON______

(I have changed spaces to '_' and tabs to '|' so you can see better).

I'm not aware of any way to change this behaviour. A common way to get tab-delimited output without spaces is to select it that way:

SELECT deptno||CHR(9)||dname||CHR(9)||loc AS record
FROM dept;

RECORD
---------------------
10|ACCOUNTING|NEW YORK
20|RESEARCH|DALLAS
30|SALES|CHICAGO
40|OPERATIONS|BOSTON

Use SET TRIMSPOOL ON to remove the trailing spaces on the last column.|||Hi andrew,

Thanks for your help. If I have 100+ columns in my select statement, will using concatenate affect the performance of the select?

Cheers,

Pete|||Originally posted by peisiong
Hi andrew,

Thanks for your help. If I have 100+ columns in my select statement, will using concatenate affect the performance of the select?

Cheers,

Pete
Not as far as I know.

How to separator the ODBC and SQL client

I have one SQL server 2000 , and some client connect to SQL server through ODBC Client and use ACCESS to query database ,some client can use SQL server 2000 client to manage the database. Now I don't want the ODBC client install SQL client and connect to
SQL server 2000. I have install a host firewall in SQL server,but because ODBC client and SQL client can use two way (name pipe and TCP port 1433),so I also can't reject ODBC client use SQL client. Does someone any suggestion.
Depending on your environment several possibilites come to mind.
You can take out named pipe connections all together and only allow TCP/IP connections to your SQL server. Client DSNs used by Access are frequently set up to used named pipe connections instead of TCP/IP.
You can reassing SQL to use some other than the standard port '1433' - some higher number preferably.
You can hide the SQL port all together (Using Server Network Utility) This will most certainly also cause disruption for the already existing SQL client connections. You can also just monitor the current connections to your SQL server and isolate the non
SQL clients one at a time by isolating their connection properties.
|||Many thanks Sassan!
I can disable the port 1433 or name pipe, but I must enable the client connect to the SQL Server use ODBC, but how can I limit the user only connect the SQL server through ODBC, and reject the sql client connect one the same computer.
|||There is not a method to do this. If a client can connect from one
application he can also connect form any other application if he has a
login and knows the name of the SQL Server machine.
Rand
This posting is provided "as is" with no warranties and confers no rights.

How to separator the ODBC and SQL client

I have one SQL server 2000 , and some client connect to SQL server through O
DBC Client and use ACCESS to query database ,some client can use SQL server
2000 client to manage the database. Now I don't want the ODBC client install
SQL client and connect to
SQL server 2000. I have install a host firewall in SQL server,but because OD
BC client and SQL client can use two way (name pipe and TCP port 1433),so I
also can't reject ODBC client use SQL client. Does someone any suggestion.Depending on your environment several possibilites come to mind.
You can take out named pipe connections all together and only allow TCP/IP c
onnections to your SQL server. Client DSNs used by Access are frequently set
up to used named pipe connections instead of TCP/IP.
You can reassing SQL to use some other than the standard port '1433' - some
higher number preferably.
You can hide the SQL port all together (Using Server Network Utility) This
will most certainly also cause disruption for the already existing SQL clien
t connections. You can also just monitor the current connections to your SQL
server and isolate the non
SQL clients one at a time by isolating their connection properties.|||Many thanks Sassan!
I can disable the port 1433 or name pipe, but I must enable the client conne
ct to the SQL Server use ODBC, but how can I limit the user only connect th
e SQL server through ODBC, and reject the sql client connect one the same co
mputer.|||There is not a method to do this. If a client can connect from one
application he can also connect form any other application if he has a
login and knows the name of the SQL Server machine.
Rand
This posting is provided "as is" with no warranties and confers no rights.

How to separator the ODBC and SQL client

I have one SQL server 2000 , and some client connect to SQL server through ODBC Client and use ACCESS to query database ,some client can use SQL server 2000 client to manage the database. Now I don't want the ODBC client install SQL client and connect to SQL server 2000. I have install a host firewall in SQL server,but because ODBC client and SQL client can use two way (name pipe and TCP port 1433),so I also can't reject ODBC client use SQL client. Does someone any suggestion.Depending on your environment several possibilites come to mind
You can take out named pipe connections all together and only allow TCP/IP connections to your SQL server. Client DSNs used by Access are frequently set up to used named pipe connections instead of TCP/IP
You can reassing SQL to use some other than the standard port '1433' - some higher number preferably
You can hide the SQL port all together (Using Server Network Utility) This will most certainly also cause disruption for the already existing SQL client connections. You can also just monitor the current connections to your SQL server and isolate the non SQL clients one at a time by isolating their connection properties.|||Many thanks Sassan
I can disable the port 1433 or name pipe, but I must enable the client connect to the SQL Server use ODBC, but how can I limit the user only connect the SQL server through ODBC, and reject the sql client connect one the same computer.|||There is not a method to do this. If a client can connect from one
application he can also connect form any other application if he has a
login and knows the name of the SQL Server machine.
Rand
This posting is provided "as is" with no warranties and confers no rights.