POS does not start after change of db collation rms2.0 sql2005

Oct 11, 2007 3 Replies

found out that db collation and server collation differ giving trouble when importing csv at stocktake (collation error on join). so I changed collation to the default sql2k one Latin1 etc.. (so server and db match) (from sql_....) this works fine but when starting the POS it reports immediately 'row could not be found or could be altered", and the pos program exits straight away.



any clues how to solve?



Thanks Gosling


It has been changed from: SQL_Latin1_General_Cp1_CI_AS to Latin General Cl AS

I have d> hi Gosling, I have doubt that they are using in the bussiness logic some

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required