Collation Problems

I am not able to fix this Collation Problem. After reading the questions and answers on this site I came to know that I have to install Unicode_Hotfix_cp850bin2 hotfix. I got the Sneak Preview software from the ftp site ftp://ftp.sap.com/pub/sdn/devkits/EP_DevEdition_SneakPreview/. The zip file on this site do not have MSS-hotfixes folder that gives the MS Sql server hot fix for collation problem SQL_Latin1_General_CP850_BIN2. I installed Sql Server 2000 Service Pack 3. The collation in the instance shows SQL_Latin1_General_CP850_BIN. Can somebody help.
Thanks
Venkat Dittakavi

Hi
The problem occurs when u install MS SQL for the first time
you need to choose the custom method, not default installation, with the custom method the screens appear
to choose the binary collation needed.
Should you go ahead the j2ee installation fails saying it required the collation to be correct. Rather uninstalled and fix the error then do ahead
Regards
Arun

Similar Messages

Collation problem in Acrobat Reader X

I have a collation problem with Acrobat Reader X and HP LaserJet M2727 nf (using HP Universal Printing PCL 6 driver)
When printing multiple copies of a PDF, the result is always in the order 1,2,3 1,2,3 etc. (for a 3 page document for example)
This is the case even when I uncheck the default collate option.
How can I disable the collation option in this version?
Thanks,
Eran

HELP! This is a killer problem. Everyone is banking on PDF documents and Adobe Reader. YOU CAN NOT IGNORE THIS ANY MORE!
There was a registry setting in Reader 8 to force host collation.. it doesn't work any more. Please respond immediately !!!!

Portal 7.0 Installation Problem-MS SQL 2005 Collation Problem

Hi,
We are installing Portal 7.0 on MSSQL 2005.while installing ,we are facing the MSSQL collation problem.The error is
"Required MSSQL Collation for the SAP System Installation is:
SQL_Latin1_General_CP850_BIN2.
Your Server uses collation:SQL_Latin1_General_CP1_CI_AS."
Regards,
Bala.

Hi,
When installing SQL Server 2005, u need to select "Binary order based on code point comparison (use with 850 multilingual character set).
As pointed above, re-install ur SQL server and EP7.0
Regards,
Fahad

IKM MSSQL Incremental Update fails on SQL Server 2000 - Collation Problem

I am having a problem where the the incremental update isn't cabable of updating the table it creates.
In the Flag Rows to Update I get the following error message:
446 : HY000 : java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Cannot resolve collation conflict for equal to operation.
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Cannot resolve collation conflict for equal to operation.
Source Code is:
update     S
set     IND_UPDATE = 'U'
from     SQRoracleStage..I$_tblOracleStage      S,
     SQRoracleStage..tblOracleStage      T
where     T.Occurance     = S.Occurance
and     T.PlanName     = S.PlanName
Oracle has suggested that the IKM be updated to include a COLLATE clause following the column name in the where clause.
update S
set IND_UPDATE = 'U'
from <%=snpRef.getTable("L", "INT_NAME", "A")%> S,
<%=snpRef.getTable("L", "TARG_NAME", "A")%> T
where <%=snpRef.getColList("", "T.[COL_NAME]\t= S.[COL_NAME] COLLATE replace_with_server_collation_string", "\nand\t", "", "UK")%>
However this code doesn't retrieve the collation string, but rather expects you to replace the replace_with_server_collation_sting with the value from the server.
Being unfamiliar with SQL Server I would have expected that the model should be capable of determining this value, and that the code should look something similar to:
update S
set IND_UPDATE = 'U'
from <%=snpRef.getTable("L", "INT_NAME", "A")%> S,
<%=snpRef.getTable("L", "TARG_NAME", "A")%> T
where <%=snpRef.getColList("", "T.[COL_NAME]\t= S.[COL_NAME] COLLATE <%=snpRef.getServerCollationString("L", "TARG_NAME", "A")%> ", "\nand\t", "", "UK")%>
It seems as though since ODI creates the table dynamically it should be capable of doing an update to it without intervention.
Has anyone found a work around for this issue?

I found the error :)
This is what happened:
I copied the tables from the MS SQL Server model to my Oracle model and then generated the DDL, so this gave me a quick set of tables in Oracle identical to the MS SQL database. But what I didn't know was that with the reverse engineer from MS SQL the ODI tool set the primary key columns to READ ONLY (and thus my copied tables also had read only primary key columns). Read only is OK for a source table but devastating for my tables I must load. So when I removed the read only indicator from the Oracle target table pk columns I was again a happy camper !
Thanks for being the one to talk to ! That really helped :)

Collation problem on BPC migration.

We are doing a migration from V4.2 to V7.0 BPC on microsoft plataform.
The new database has the correct collation 'SQL_Latin1_General_CP1_CI_AS' but the V4.2 back up was from a database which collation is 'Finnish_Swedish_CI_AS'
Now we have problems with column collation in the restored backup. We can't change column collation because there are index using the columns.
Anybody have any idea how to proceed? We strongly appreciate it.
Best Regards.

Hi dude!
In fact, you can run program InstColl.exe to convert to SQL_LATIN1_GENERAL_CP850_BIN2, but unfortunately it does only run on a SQL Server 2000 SP4 database. Then:
(a) if your database is SQL Server 2000 but you did not apply SP4, you should apply it and then run the instColl.exe.
(b) if your original database was SQL Server 2000, but you upgraded e.g. to SQL Server 2005/2008, you can restore a backup on a SQL Server 2000 SP4 database instance; then you will be able to run instColl.exe and only after having run it you will be able to upgrade to SQL Server 2005/2008.
(c) if your database is other than SQL Server 2000, e.g. SQL Server 2005, the only option is to export the entire database and then import it with the correct collation (just like in a system copy) by means of R3trans, as unfortunately you cannot detach a SQL Server 2005 database and then attach it to a SQL Server 2000.
Find the details in SAP notes 505906 and 600027.
Cheers!!
-Jesú

2004C Collation problem

Hi,
As you known,in 2004C, the default Collation is SQL_Latin1_General_CP850_CI_AS. My SQL server 2000 uses Hungarian_CI_AS.
I want to use stored procedures, but I have a problem with parameters containing characters "ő","ű","Ő","Ű". It looks like they change to "o","u","O","U".
Please help!
Szilard

hi,
select
from
where
Field1 = @param1 collate Hungarian_CI_AS
and
Field2 = @param2 collate Hungarian_CI_AS
hope this help

Changing a column collation - problems?

Hello,
I have a VFP database that was migrated to SQL Server 2012. One of the VFP table's PK's utilized uppercase and lowercase values to distinguish rows, which of course does not fly by default in SQL Server.
Rather than having to redesign this part of the application and go through a data conversion, I'm thinking of changing the collation of this PK column and related FK fields to be case sensitive. On the surface it sounds like this would solve my
issue and the app would function as it always has.
Is there anything that would make me think twice about doing this?
Thanks.
Bill

Hi,
Be aware that changing collation at individual fields may break your queries.
Look at the following sample :
USE YourTestDB
SET NOCOUNT ON
SET ANSI_NULLS ON
SET QUOTED_IDENTIFIER ON
SET ANSI_PADDING ON
CREATE TABLE tblX(X CHAR(10) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL, CONSTRAINT PK_tblX PRIMARY KEY CLUSTERED (X ASC))
CREATE TABLE tblY(Y CHAR(10) COLLATE Latin1_General_100_BIN NOT NULL, CONSTRAINT PK_tblY PRIMARY KEY CLUSTERED (Y ASC))
INSERT INTO tblX VALUES ('A');
INSERT INTO tblX VALUES ('B');
INSERT INTO tblX VALUES ('C');
INSERT INTO tblX VALUES ('D');
INSERT INTO tblX VALUES ('E');
INSERT INTO tblY VALUES ('A');
INSERT INTO tblY VALUES ('C');
INSERT INTO tblY VALUES ('E');
INSERT INTO tblY VALUES ('G');
INSERT INTO tblY VALUES ('I');
SELECT tblX.X, tblY.Y FROM tblX INNER JOIN tblY ON tblX.X = tblY.Y
-- Gives the following error
-- Msg 468, Level 16, State 9, Line 20
-- Cannot resolve the collation conflict between "Latin1_General_100_BIN" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation.
-- You'll have to rewrite your query as follows
SELECT tblX.X, tblY.Y FROM tblX INNER JOIN tblY ON tblX.X COLLATE Latin1_General_100_BIN = tblY.Y
-- Or
SELECT tblX.X, tblY.Y FROM tblX INNER JOIN tblY ON tblX.X = tblY.Y COLLATE SQL_Latin1_General_CP1_CI_AS
Sebastian Sajaroff Senior DBA Pharmacies Jean Coutu

Collation problem for sql queries

Hi All,
We have 1 old database which have collation "Latin1_General_100_CI_AS".
We have moved this DB to other server & on for this DB collation is "Latin1_General_100_CS_AS"
There are lots of SQL procedure we had written & all table,field name in case insensitive manner.
so for new db it will give us error invalid object name because this db is set as "Latin1_General_100_CS_AS".
Now we can not change the collation of db.
so please know us how we can achive case insensitivity for object name in query for "Latin1_General_100_CS_AS" collation.
please help us we are stucked in big issue & it is not easy to change Store procedure as Senstive name of object.

Anybody have another suggestion for JK?
Thanks!
Ed Price, Azure & Power BI Customer Program Manager (Blog,
Small Basic,
Wiki Ninjas,
Wiki)
Answer an interesting question?
Create a wiki article about it!

DW8 and Recordset collation

Hi everyone
My problem is not new but i didn't solve it completely. When
i working with PHP MySQL server model in Dreamweaver 8 i have the
collation problem with results on my pages. It can be well when the
adding this code after mysql_select_db() line in the pages.
the fixing code is;
mysql_query("SET NAMES 'latin5'");
well, problem was solved however the recordset is damaged in
DW Bindings panel and i didn't use the drag-drop properties
anymore.
I wonder that, the developer can add collation support for
PHP MySQL recordsets in DW for new versions or publish a fix
extension for this problem. It would be so nice, wouldnt it?
whatever i try the modify the DW's ServerBehaviors commands
for this, it was worked but a mysql error appear on the Bindings
panel. I changed ~Dreamweaver
8\Configuration\ServerBehaviors\PHP_MySQL\Recordset_main.edml
source code for first step and i get this error message from
bindings panel. Is there anyone has idea for solves of this
problem. It can be very helpful for other collation needed
developers :)
thanx everyone already now

i made an extension for this please check this out
http://www.dw.gen.tr/?module=files&page=download&id=275
for screenshot:
http://www.dw.gen.tr/?module=site&page=img_show&id=498

Database Collation VS Column Collation

I have some Collation problem I need a help, please!
I have two SAME test databases,
but one (A) has a Collation set to Hebrew_CI_AS, and another one (B) - SQL_Latin1_General_CPT1_CS_AS.
Both databases have a Synopsis table with a column NVARCHAR(1000), holding programmes EPG.
In database (A) the COLUMN's Collation is set to SQL_Latin1_.... ( an opposit to the database ! )
In database (B) the COLUMN's Collation is set to Hebrew_CI_...  (again - an opposit to the database)
My problem is:
When I want to update this column on databse (A) with special latin tags, f.e. ñç, I get question marks only: UPDATE A..Synopsis SET ... = 'Pour Bébé' shows me Pour B?b?
On the other hand, if in database (B)  I want to type some Hebrew carachters, I get ???????? as well.
It seems that despite I have a specified collation on my column, SQL keeps ignore it.
How can I fix it?
Many thanks in advance

My problem is:
When I want to update this column on databse (A) with special latin tags, f.e. ñç, I get question marks only: UPDATE A..Synopsis SET ... = 'Pour Bébé' shows me Pour B?b?
On the other hand, if in database (B)  I want to type some Hebrew carachters, I get ???????? as well.
I see Ed bumped this old unanswered thread. Even though you've probably since resolved the issue, I'll answer it to help others that may run into the same issue.
Collation affects non-Unicode string literals and the characters that can be stored for non-Unicode columns (char and varchar). Unicode columns (nchar and nvarchar) can store all the characters you mentioned properly.  The character conversion
problem occurs here because you are you are not indicated a Unicode character string literal so the value is interpreted as an non-Unicode string literal and converted according to the database default collation.
To fix the problem, prefix the literal string with an N to indicate a Unicode string line the example below. If the SQL is executed from a client application, the best solution is to use properly typed parameters instead of string literals.
SET ... = N'Pour Bébé'
Dan Guzman, SQL Server MVP, http://www.dbdelta.com

Problems with collation when searching

Hi,
We have set up our database with the collation Danish_Norwegian_CI_AS, but we are having trouble when searching for data containing 'AA'. In order to get the rows out, we need to change the collation to eg. SQL_Latin1_General_CP1_CI_AS
I have set up a fiddle, to show the problem, please run each select and match the result:
http://sqlfiddle.com/#!6/4218c/10/0
Does anyone know how to fix this without changing the server collation.
Thanks
H_H

A little searching reveals that AA has a special meaning in Danish:
AA and danish collation
like AA
Note that you can dynamically set the collation for sorting or comparision purposes using the collate clause in your query. While we're at it, collation is set at the COLUMN level, though higher level settings exist but only have an effect
in certain circumstances. Changing the server collation will not solve your problem since it will not affect your existing databases, tables, and columns within those tables. And be careful about changing collation since it will affect sorting.

Problem : Cannot resolve the collation conflict between ...

Hi
I want select a column from another database base on my current field on current database.
here is my query :
select ms.ServiceID, ms.ServiceName, ms.CoefficientFixedService,
(select Services_Name from MpAdmisson..IAServices_Table where Services_DepartmentID=24 and Services_Name=ms.ServiceName) as N'MpServiceName'
from MedicalServices ms
join MedicalCategories mc on ms.MedicalCategorizationID=mc.MedicalCategorizationID
join Zones z on mc.ZoneID=z.ZoneID
where z.ZoneID=24
but I'm facing this error :
Cannot resolve the collation conflict between "Persian_100_CI_AI" and "Arabic_CI_AS" in the equal to operation.
Also i changed collation of "MpAdmisson" db to "Persian_100_CI_AI" and even restart msSqlServer service, but i'm facing the same error!
where is my problem and how to solve it ?
thanks in advance
http://www.codeproject.com/KB/codegen/DatabaseHelper.aspx

although you changed the collation of the database it does not mean that all the objects changed their collation too automatically.
So far you are correct.
The change is only done when you change the data within the objects, thus recreating the table and moving data in / out or touching each and every value with doing something on the values themselves (the following will not work UPDATE (..) SET ServiceName
= ServiceName, the optimizer is smart enough too see that as a noop).
However, this is flat wrong. This is the story: each character column in a database has a collation tied to it. When you change the collation of a database, you change 1) the collation of the columns in the system tables. 2) The default collation. To change
the collation on the individual columns, you need to alter the column:
ALTER TABLE IAServices_Table
ALTER COLUMN Services_Name <current data type> COLLATE Persian_100_CI_AI [NOT] NULL
Unfortunately, this only works if the column is not indexed and has no constraints tied to it. Any indexes have to be dropped and recreated after the ALTER statement. If the column is a key column and there are referencing foreign keys, they also have to
be dropped and recreated. Thus, this is quite a far-reaching operation. And it may not stop there - with some amount of bad luck, constraints may fail with the new collation.
For this reason, this workaround suggested by Jens, may be your only option in the short term:
If you cannot do this currently, you can still do the following and collate on a per query basis:
select ms.ServiceID, ms.ServiceName, ms.CoefficientFixedService,
(select Services_Name from MpAdmisson..IAServices_Table where Services_DepartmentID=24 and Services_Name=ms.ServiceName COLLATE Persian_100_AS_CI) as N'MpServiceName'
from MedicalServices ms
And this part of Jens's post is correct. To note though is that use of the COLLATE clause voids any index on ServiceName. (Since this index is sorted according the rules of Arabic, and not the rules of Farsi.)
Erland Sommarskog, SQL Server MVP, [email protected]

Collation finnish_swedish and Danish chars. Problem

We have a problem with current collation of database finish_swedish doesn’t recognize Danish letter
æ and treats it as 2 letters ae.
As example: grae.dk and græ.dk is the same in the Eyes
of my SQL-server :)
We couldn’t find any bigger subset of collation which includes all but not BIN
Anyone can help me out with this?

Hi were running SQL Server 2012 SP1, Swedish_finnish collation.
USE [master]
GO
/****** Object: Database [database] Script Date: 2014-08-11 16:58:11 ******/
CREATE DATABASE [database]
COLLATE Finnish_Swedish_CI_AS
CONTAINMENT = NONE
ON PRIMARY
( NAME = N'dotabase', FILENAME = N'E:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\database_prod_bak.mdf' , SIZE = 8919168KB , MAXSIZE = UNLIMITED, FILEGROWTH = 10%)
LOG ON
( NAME = N'database_log', FILENAME = N'E:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\database_prod_bak_log.ldf' , SIZE = 1193344KB , MAXSIZE = 2048GB , FILEGROWTH = 10%)
GO
ALTER DATABASE [database] SET COMPATIBILITY_LEVEL = 110
GO
IF (1 = FULLTEXTSERVICEPROPERTY('IsFullTextInstalled'))
begin
EXEC [database].[dbo].[sp_fulltext_database] @action = 'enable'
end
GO
ALTER DATABASE [database] SET ANSI_NULL_DEFAULT OFF
GO
ALTER DATABASE [database] SET ANSI_NULLS OFF
GO
ALTER DATABASE [database] SET ANSI_PADDING OFF
GO
ALTER DATABASE [database] SET ANSI_WARNINGS OFF
GO
ALTER DATABASE [database] SET ARITHABORT OFF
GO
ALTER DATABASE [database] SET AUTO_CLOSE OFF
GO
ALTER DATABASE [database] SET AUTO_CREATE_STATISTICS ON
GO
ALTER DATABASE [database] SET AUTO_SHRINK OFF
GO
ALTER DATABASE [database] SET AUTO_UPDATE_STATISTICS ON
GO
ALTER DATABASE [database] SET CURSOR_CLOSE_ON_COMMIT OFF
GO
ALTER DATABASE [database] SET CURSOR_DEFAULT GLOBAL
GO
ALTER DATABASE [database] SET CONCAT_NULL_YIELDS_NULL OFF
GO
ALTER DATABASE [database] SET NUMERIC_ROUNDABORT OFF
GO
ALTER DATABASE [database] SET QUOTED_IDENTIFIER OFF
GO
ALTER DATABASE [database] SET RECURSIVE_TRIGGERS OFF
GO
ALTER DATABASE [database] SET DISABLE_BROKER
GO
ALTER DATABASE [database] SET AUTO_UPDATE_STATISTICS_ASYNC OFF
GO
ALTER DATABASE [database] SET DATE_CORRELATION_OPTIMIZATION OFF
GO
ALTER DATABASE [database] SET TRUSTWORTHY OFF
GO
ALTER DATABASE [database] SET ALLOW_SNAPSHOT_ISOLATION ON
GO
ALTER DATABASE [database] SET PARAMETERIZATION SIMPLE
GO
ALTER DATABASE [database] SET READ_COMMITTED_SNAPSHOT ON
GO
ALTER DATABASE [database] SET HONOR_BROKER_PRIORITY OFF
GO
ALTER DATABASE [database] SET RECOVERY FULL
GO
ALTER DATABASE [database] SET MULTI_USER
GO
ALTER DATABASE [database] SET PAGE_VERIFY CHECKSUM
GO
ALTER DATABASE [database] SET DB_CHAINING OFF
GO
ALTER DATABASE [database] SET FILESTREAM( NON_TRANSACTED_ACCESS = OFF )
GO
ALTER DATABASE [database] SET TARGET_RECOVERY_TIME = 0 SECONDS
GO
ALTER DATABASE [database] SET READ_WRITE
GO
USE [database]
GO
/****** Object: Table [database1].[Domain] Script Date: 2014-08-11 16:58:41 ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
SET ANSI_PADDING ON
GO
CREATE TABLE [database1].[Domain](
[domainId] [varchar](32) NOT NULL,
[domain] [nvarchar](80) NOT NULL,
[created] [datetime] NOT NULL,
[modified] [datetime] NOT NULL,
[expires] [datetime] NOT NULL,
[state] [nvarchar](50) NOT NULL,
[createdBy] [nvarchar](255) NULL,
[modifiedBy] [nvarchar](255) NULL,
[accountID] [bigint] NULL,
[paidUntil] [datetime] NOT NULL,
[activeLifecycle] [varchar](255) NULL,
[registryCreationDate] [datetime] NULL,
[label] [nvarchar](50) NULL,
[isPrivateWhois] [bit] NOT NULL,
CONSTRAINT [PK__Domain__4A8948710519C6AF] PRIMARY KEY CLUSTERED
[domainId] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, FILLFACTOR = 90) ON [PRIMARY],
CONSTRAINT [IX_Domain] UNIQUE NONCLUSTERED
[domain] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, FILLFACTOR = 90) ON [PRIMARY],
UNIQUE NONCLUSTERED
[domain] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, FILLFACTOR = 90) ON [PRIMARY]
) ON [PRIMARY]
GO
SET ANSI_PADDING OFF
GO
ALTER TABLE [database1].[Domain] ADD DEFAULT ((0)) FOR [isPrivateWhois]
GO
ALTER TABLE [database1].[Domain] WITH CHECK ADD CONSTRAINT [FK__Domain__accountI__37FF1041] FOREIGN KEY([accountID])
REFERENCES [users].[Account] ([id])
ON UPDATE CASCADE
GO
ALTER TABLE [database1].[Domain] CHECK CONSTRAINT [FK__Domain__accountI__37FF1041]
GO
ALTER TABLE [database1].[Domain] WITH CHECK ADD CONSTRAINT [FK__Domain__activeLi__3AA90691] FOREIGN KEY([activeLifecycle])
REFERENCES [lifecycles].[DomainLifeCycleData] ([lifeCycleID])
GO
ALTER TABLE [database1].[Domain] CHECK CONSTRAINT [FK__Domain__activeLi__3AA90691]
GO

Problem with collate function to print booklets in Indesign

I want to print on A4 paper, two copies of booklets (150pages) A5 format. This job I want to do more (100-300 ) times.
I use ctrl+ P, copies two, in setup printer I use page size A5, output size A4, booklet printing.
If I print the document from CS2 version, I got two booklets on A4 papers, on left side of papers is one booklet, and on right side of papers is second booklet. I just cut the papers on half and I got two booklets. Next gluing the booklets is ok
If I print the same document from CS3 or CS6 version, with same print presets !!, I got two booklets, but one booklet is on both sides of A4 papers, and second booklet is also on both sides of A4 papers. I cut the A4 papers and must every half booklets put together.
Also with gluing is little problematic.
Please if someone know , where is the problem with printing? How to use print in CS3 or CS6 , to get result like in CS2 ?

As far as I recall, ID has never been able to do 2-up booklet printing from a 1-up file. I generally create a second document, then place the first one into it twice.

Problems with collate print in CS4/windows

I have to make 200 booklets in InDesign, but since i have got CS4 I can´t collate. I print 200 pages of page 1 and then 200 page of page 2 and so on. It it a large job to make booklets out of that afterwards. In my old version it was a piece of cake and just worked......
Do any of you have the solution for that????

Try opening CS3 and trying it there just for a few pages, make sure it's working.
Then Define a Print Setting based on these settings, and then import that setting into CS4.
From the Print Dialog box you can "Save Preset"
Then go to File>Print Presets>Define and then save the preset to your hard drive
Then in CS4 go to File>Print Presets>Define and import that preset.
See if that does it?
I think you're just missing a switch in Cs4 to do it, but that should work considering it's using the same settings used in CS3.

Collation Problems

Similar Messages

Maybe you are looking for