A quick google search of error 468 says this is a collation order problem.  Your company was set up in SQL as binary collation and should be case insensitive, or vice-versa.

Thanks Jay, the collation of this db is  set  to  Latin1_General_BIn as recommended by the Installation and administrative guide.  However, it does mentioned it could be also set as Latin1_general_ci_as for English language support.  does that mean is should change it?  is this normal that one database could be ci_as while others are case senstive/binary.

In my Sage world, Latin1_general_ci_as is the default, binary is the exception, but let's leave that alone for now.

ARDINVO is a simple form that's hard to mess up, unlike datapipe reports like OEINV01.  My suggestion is that you start over with a clean ARDINVO file and make your change again.  When you edit it inside Crystal, for your ODBC DSN use login/password, not NT authentication, and don't attach non-Sage tables.

okay thanks.  i will try it.  so the recommended is not necessarily what reality is then, i guess.