Getting around Case Sensitive filtering

justincale · 2007-05-30

Hi All,

I have a new Nav client for which i will be training on filter techniques. These guys are pretty lazy and i know they will not want to add an @ to the beginning of the filter to make it case INsensitive. I have read on some other posts that making the SQL database Case INsensitive will get around this problem. My question is, has anyone had experience with doing this? Does anyone know whether this will cause problems in other area's?

Item descriptions for this company have come from a legacy system and are all over the place (ie: COKE, Coke, COCA Cola, COCA COLA etc)....

ara3n · 2007-05-30

another option is to write a routine to make the description lowercase.

fl · 2007-05-30

Case and accent insensitive in SQL database works very fine.

Do also hate all that case and accent sensitive stuff if looking for a record.

Option to make description lowercase is just a solution for description field. SQL server property, is a solution for whole application without any modification

thaug · 2007-05-30

Our SQL database has been case insensitive from the beginning with no problems. The only think I can think of that could be a problem is if you have something that is case sensitive as the primary key to a table. So, if you have one record that is in as Coke, and another that is in as COKE, switching to case insensitive may cause a problem.

fl · 2007-05-30

if you have something that is case sensitive as the primary key to a table.

But a practice like that asks for prblems. As primary key, allways use code or integer fields. Look for all the standard Navision tables how they primary key is build.

Howdy, Stranger!

Quick Links

Categories

Getting around Case Sensitive filtering

Comments