string - Odd Oracle + .net behaviour when comparing types -

In my workplace, there is a pure application provided to us by the Postal Service, from an Oracle database running on the same machine Joins and is responsible for registering, storing and printing shipping labels.

Viewing as a database host etc. is configurable. We asked the company whether the application can be used on the network (just copying it to another machine "Verbatim does not match the format string" errors), we were told that "this is not possible". To answer no, I poked around the exe with the consultant.

With the v $ sqlarea view of Oracle I pinpointed errors for some date comparison tasks, but I do not know why the application was working on the first place on the original machine.

The original application

SELECT * uses the same queries as shipping WHERE dated = '03.03.2011' - Error

Easily fixed with something

SELECT * to shipping WHERE to_char (Date, 'yyyy / mm / dd') = '2011/03/28' >

Why does the original application work without any error? The wrong query comes in v $ sqlarea view when the application is used on the original host, if I copy the query and do anything to run it manually, then it throws the error, if I do any Also error in the application on other machines, is there some setting in Oracle that is modifying questions on the fly, but for questions starting from the local machine, while $ $ sqlar When storing the original query in ea?

It looks like a regional setting difference between the two client machines, because the dates are formatted Which will be used to convert the culture into a string in NIT. , And as long as this app does not specify a culture, then the user running this application will use the logon setting on it. This is definitely a problem if the database engine is expecting them in a certain format. This problem is less likely to be derived from parametric queries, where the date parameters are different from the query and passed as a date datatype instead of a string.