May 10, 2009 at 4:00 pm
We are using a legacy routing tool and we have moved the backend database from 2000 to 2005.
The legacy code is complied so we are not able to alter it.
There are two parts to the application and one part is expecting to connect with the password of mixed case (Aaaaa) and the other all upper case (AAAAA). the programmers have hardcoded this into the code!!!!!!! is there anyway to make sqlserver 2005 case insensitive on the password???
May 14, 2009 at 2:24 pm
This is solved!
May 14, 2009 at 8:42 pm
How was it solved?
K. Brian Kelley
@kbriankelley
May 15, 2009 at 7:45 am
with the consent of the vendor who no longer has that version of the source code, hexeditor on dll, changed upper case instance to lower.
May 15, 2009 at 8:14 am
after listening to that type of fix I think that it may be time to begin the search for a new application vendor ...
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply