There are several possible solutions here:

http://stackoverflow.com/questions/230138/sql-server-make-all-upper-case-to-proper-case-title-case

I like the solution involving the sequence table and no looping.

CREATE FUNCTION String.InitCap( @string nvarchar(4000) ) RETURNS nvarchar(4000) AS

BEGIN

-- 1. Convert all letters to lower...

You should be able to do that through Policy Based Mgmt (PBM). Look into that and test it out.

That is good to hear. Glad we could help.

Tom.Thomson (9/15/2011)

---

Steve Jones - SSC Editor (9/15/2011)

---

Please let's not have quotes of every post that counts down from 95, 94, 93.

I'm going out of town for a few days. I'm...

You're welcome.

Here is a tutorial on that

http://whiteknighttechnology.com/cs/blogs/brian_knight/archive/2006/03/03/126.aspx

Try this

http://www.sqlis.com/post/Looping-over-files-with-the-Foreach-Loop.aspx

You can apply it directly. There is usually an update for that via microsoft update.

Here is a tutorial on one such solution.

http://microsoft-ssis.blogspot.com/2011/01/use-filedates-in-ssis.html

Yes do a date comparison - but you will need to specify just the date part of that getdate() and ignore the time part.

As for the ForEachLoop - yes. ...

K

One of two things has worked well for me. Either use a for each file enumerator and bring in all of the file names - then pick the file...

Curses the text editor. I deleted that %.

Anyway,

where and how is that expression being used? Is it within a data flow or as part of a proc?

You are specifying in your statement to look for a file based on Year,Month,Day and time

"//jls-devprescnt\\xxxxx\\"+(DT_WSTR,4)DATEPART("yy",getdate())+

RIGHT("0"+(DT_WSTR,2)DATEPART("MM",getdate()),2)+

RIGHT("0"+(DT_WSTR,2)DATEPART("dd",getdate()),2)+" "+

RIGHT("0"+(DT_WSTR,2)DATEPART("hh",getdate()),2)+

RIGHT("0"+(DT_WSTR,2)DATEPART("mi",getdate()),2)+

RIGHT("0"+(DT_WSTR,2)DATEPART("ss",getdate()),2)+

"_01A.txt"

The three commented lines are causing your issue. You need to remove those...

Also, when inserting these characters into the database - are you specifying that the values are unicode?

e.g.

Insert Into Sometable (MyNCharField)

Select N'someValue')

Are you selecting the data through a query, or are you opening the table in SSMS such that you can click and edit the data?