Case Sensitivity in "Find"

I know I am not the only one that has had a problem with Bridge CS3 and the "Find" function. The "Find" function in CS3 is case sensitive and it was not in CS2. Has anyone found a fix or work around for this problem(other than doing mulitple searches)? I don't understand why this was changed. It appears that it's a "bug". It's difficult to advocate using Adobe products to view and label images when "Find"ing them later is painful. Is there a solution?

Curt and John,
I'm sorry I didn't specify this earlier. The difference may be that I am using "All Metadata" as the selection under "Criteria". I do not have a problem if I am searching "Keywords" or "Copyright Notice". I am often searching for "Creator" so I use "All Metadata". If I enter "howard" I will get zero results. If I enter "Howard" I get five selections. If this works differently on yours then there must be a preference setting that I can't find.
Thanks for your attention...

Similar Messages

There is a problem with firefox find option in new version ! i have noticed after updating to the new version the find option has become case sensitive

Now the find option in the firefox page which can be activated by pressing F3 is Case sensitive and this caused me a lot of problems
this problem wasnt there in older firefox versions

Sorry, that "mail" thing isn't a standard part of Firefox. Seek support from the developer of the add-on you have installed that added that feature to Firefox. Support contact information should be on the download page for that extension.

Is a Full Text Index search case sensitive or not in SQL Server 2012?

I setup full text index on my contact table and am attempting to run a search on it using the following query:
SELECT *
FROM sysdba.Contact C
WHERE CONTAINS(C.FirstName, 'Test')
OR CONTAINS(C.LastName, 'Test')
The problem is it's clearly running a case sensitive search. I did a quick search to find out how to change it to be case in-sensitive and found two pages (both for SQL Server 2012) with conflicting answers:
1 - MSDN - "Query with Full-Text Search" - http://msdn.microsoft.com/en-us/library/ms142583(v=sql.110).aspx
Case sensitivity
Full-text search queries are case-insensitive. However, in Japanese, there are multiple phonetic orthographies in which the concept of orthographic normalization is akin to case insensitivity (for example, kana = insensitivity). This type of orthographic normalization
is not supported.
1 - TechNet - "Full-Text Search (SQL Server)" - http://technet.microsoft.com/en-us/library/ms142571(v=sql.110).aspx
Full-text queries are
not case-sensitive. For example, searching for "Aluminum" or "aluminum" returns the same results.
Can someone please explain this? Is it possible to do it without it being case sensitive? If yes, how?
(Sorry, I couldn't make those links b/c TechNet hasn't verified my account)
Thank you for your time and help,
Hanan

Whats the collation setting for the columns? try using a case insensitive collation as below
SELECT *
FROM sysdba.Contact C
WHERE CONTAINS(C.FirstName COLLATE SQL_Latin1_General_CP1_CI_AS, 'Test')
OR CONTAINS(C.LastName COLLATE SQL_Latin1_General_CP1_CI_AS, 'Test')
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

How can I backup data from a case-sensitive volume to a NON-case-sensitive volume?

The case-sensitive volume in this instance being a desktop-mounted disk image volume.
A tragi-comedy in too many acts and hours
Dramatis Personae:
Macintosh HD: 27" iMac 3.06GHz Intel Core 2 Duo (iMac10,1), 12 GB RAM, 1 TB SATA internal drive
TB1: 1 TB USB external drive
TB2: 2 TB USB to Serial-ATA bridge external drive
Terabyte: a .dmg disk image and resulting desktop volume of the same name (sorry, I don't know the technical term for a .dmg that's been opened, de-compressed and mounted -- evanescently -- on the desktop)
Drive Genius 3 v3.1 (3100.39.63)/64-bit
Apple Disk Utility Version 11.5.2 (298.4)
Sunday morning (05/08/11), disk utility Drive Genius 3's drive monitoring system, Drive Pulse, reported a single bad block on an external USB2.0 1TB drive, telling me all data would be lost and my head would explode if I didn't fix this immediately. So I figured I'd offload the roughly 300 GB of data from TB1 to TB2 (which was nearly empty), with the intention of reinitializing TB 1 to remap the bad block and then move all its data BACK from TB 2. When I opened TB1's window in the Finder and tried to do a straight "Select All" and drag all items from TB1 to TB2, I got this error message:
"The volume has the wrong case sensitivity for a backup."
The error message didn't tell me WHICH volume had "the wrong case sensitivity for a backup," and believe me, or believe me not, this was the first time I'd ever heard that there WAS such a thing as "case sensitivity" for a drive. I tried dragging and dropping some individual folders -- some of them quite large, in the 40GB range -- from TB1 to TB2 without any problem whatsoever, but the majority of the items were the usual few-hundred-MB stuff that seems to proliferate on drives like empty Dunkin' Donuts coffee cups on the floor of my car, and I didn't relish the idea of spending an afternoon dragging and dropping dribs and drabs of 300GB worth of stuff from one drive to another.
Being essentially a simple-minded soul, I had what I thought was the bright idea that I could get around the problem by making a .dmg disk image file of the whole drive, stashing it on TB2, repairing and re-initializing TB1, and then decompressing the disk image I'd made of TB1, and doing the "drag and drop" of all the files in resulting desktop volume to TB1. So I made the .dmg of TB1, called "Terabyte," stashed that .dmg on TB2 (no error messages this time), re-initialized and then rebooted the iMac from my original Snow Leopard 10.6.1 disks and used Disk Utility to erase and initialize TB1 -- making sure that it was NOT initialized as case-sensitive, and installed a minimal system on TB1 from the same boot. Then I updated that 10.6.1 system to 10.6.7 with System Update, and checked to see that Disk Utility reported all THREE drives -- internal, 1TB, and 2TB -- as Mac OS Extended (Journaled), and no "case sensitive" BS. I also used Drive Genius 3's "information" function for more detailed info on all three drives. Except for the usual differing mount points, connection methods, and S.M.A.R.T. status (only the Macintosh HD internal, SATA 1TB drive supports S.M.A.R.T.), everything seemed to be oojah-***-spiff, all three drives showing the same Partition Map Types: GPT (GUID Partition Table.) Smooth sailing from here on out, I thought.
Bzzzzt! Wrong!
When I opened the Terabyte .dmg and its desktop volume mounted, I tried the old lazy man's "Select All" and drag all items from the desktop-mounted drive "Terabyte" to TB1, I got the error message:
"The volume has the wrong case sensitivity for a backup."
I then spent the next three hours on the phone with AppleCare (kids -- when you buy a Mac ANYTHING, cough up the money for AppleCare. Period.), finally reaching a very pleasant senior tech something-or-other in beautiful, rainy Portland, OR. Together we went through everything I had done, tried a few suggestions she offerred, and, at the end of three hours, BOTH of us were stumped. At least I didn't feel quite as abysmally stupid as I did at the beginning of the process, but that was all the joy I had gotten after two solid days of gnawing at this problem -- and I mean SOLID; I'm retired, and spend probably 12 hours a day, EVERY day, at the keyboard, working on various projects.
The AppleCare senior tech lady and I parted with mutual expressions of esteem, and I sat here, slowly grinding my teeth.
Then I tried something I don't know why I was so obtuse as to not have thought of before: I opened Apple's Disk Utility and checked the desktop-mounted volume Terabyte (Mount Point: /Volumes/Terabyte), the resulting volume from opening and uncompressing the .dmg "Terabyte".
Disk Utility reported: "Format : Mac OS Extended (Case-sensitive)." Doh!
Obviously, TB1, the 1 TB USB external drive I'd actually bought as part of a bundle from MacMall when I bought my 27" iMac, and which I had initialized the first day I had the iMac up and running (late November 2009), had somehow gotten initialized as a Case-sensitive drive. How, I don't know, but I suspect the jerk behind the keyboard. Whatever the case, when I created the Terabyte disk image (the drive's original name: when I erased and re-initialized it -- see above -- I renamed it "1TB" for quick identification), the original drive's "Case-sensitive" format was encoded too. So when I tried to drag and drop EVERYTHING from the desktop-mounted volume "Terabyte" to the newly initialized and "blessed" (now THERE's a term from the past!), the system recognized it as an attempt as a total volume backup, and hit me with "The volume [the desktop-mounted volume "Terabyte" -- BB] has the wrong case sensitivity for a backup." And, of course, the reinitialized TB1 was now correctly formatted as NOT "case-sensitive."
Well, that solved the mystery (BTW, Disk Utility identified the unopened Terabyte.dmg as an "Apple UDIF read-only compressed {zlib}, which is why the .dmg file could be copied to ANY volume, case sensitive or not), but it didn't help me with my problem of having to manually move all that data from the desktop-mounted volume "Terabyte" to TB1. I tried to find a way to correct the problem at the .dmg AND opened-volume-from-.dmg level with every disk utility I had, to no avail.
Sorry for the long exposition, but others may trip over this "case-sensitive" rock in the road, and I wanted to make the case as clear as possible.
So my problem remains: other than coal shovel by coal shovel, is there any way to get all the data off this case-sensitive desktop-mounted volume "Terabyte" and onto TB1.
Not that I know whether it would made any difference or not, one of the things that got me into this situation was my inability to get "Time Machine" properly configured so it wasn't making new back-ups every (no lie) 15 minutes.
Philosophical bonus question: what's the need for this "case-sensitive," "NOT case-sensitive" option for disk initialization?
As always, thanks for any help.
Bart Brown

"Am I to understand that you have a case-sensitive volume with data that you want to copy to a case-insensitive volume? And the Finder won't let you do it? If that's what the problem is, the reason should be obvious: on the source volume, you may have two files in the same folder whose names differ only in case. When copying that folder to the target volume, it's not clear what the Finder should do."
Yes, I understand all that... NOW.
What I had (have) is a USB external 1TB drive (henceforth known as "Terabyte") that I bought with my 27" iMac. I formatted, and put a minimal (to make it bootable) system on Terabyte the same day back in late November 2009 that I set up my 27" iMac. Somehow -- I don't know how -- Terabyte got initialized as "case-sensitive." I didn't even know at the time that there WAS such a thing as "case-sensitive" or "NOT case-sensitive" format.
Sunday morning (05/08/11), Drive Pulse, a toolbar-resident utility (that's Part of Drive Genius 3) that monitors internal and external drives for physical, problems, volume consistency problems, and volume fragmentation, reported a single bad block on the volume Terabyte, advising me that it would be best if I re-formatted Terabyte ASAP. I thought I could open Terabyte in a Finder window, Select All, and drag everything on the drive to ANOTHER USB external drive of 2 TB capacity (henceforth known as TB2). When I tried to do that, I got an error message:
"The volume has the wrong case sensitivity for a backup."
First I'd heard of "case sensitivity" -- I'm not too bright, as you seem to have realized.
Oddly enough (to me), I could move huge chunks of data, including a folder of 40GB, from Terabyte to TB2 with no problem.
Then the scenario unfolded per my too-convoluted message: several hours of trying things on my own, including making a .dmg of Terabyte (henceforth to be known as Terabyte.dmg) -- which left me with the exact same problem as described in the previous 4 paragraphs; and my 3 hours on the phone with AppleCare, who at least explained this case-sensitive business, but, after some shot-in-the-dark brainstorming -- tough to do with only one brain, and THAT on the OTHER end of the line -- the very pleasant AppleCare rep and I ended up equally perplexed and clueless as to how to get around the fact that a .dmg of a case-sensitive volume, while not case-sensitive in its "image" form (Terabyte.dmg), and thus able be transferred to TB1 or TB2 with no problems whatsoever, when opened -- either by double-clicking or opening in Disk Utility -- produced a desktop-mounted volume (henceforth known as the volume "Terabyte," the original name of the case-sensitive volume from which TB1.dmg had been made) that had the same case-sensitivity as the original from which it was made.
In the meantime, having gotten the data I needed to save off the physical USB "case-sensitive" volume Terabyte in the form of Terabyte.dmg, I erased and re-initialized the physical USB "case-sensitive" volume Terabyte, getting rif of the case sensitivity, and renaming it TB1. But it all left me back at square one, EXCEPT I had saved my data from the original "Terabyte" drive, and reformatted that drive to a NON- case-sensitive data now named TB1. The confusion here stems from the fact that problem case-sensitive drive, from which I made Terabyte.dmg, was originally named "Terabyte". When I re-initialized it as a NON case-sensitive drive, I renamed it TB1. I'm sorry about the confusing nomenclature, which I've tried to improve upon from my original message -- usual text-communication problem: the writer knows what he has in mind, but the reader can only go by what's written.
So, anyway, I still have the same problem, the desktop-mounted volume "Terabyte" still cannot be transferred in one whole chunk to either my internal drive, TB1, TB2, as the Finder interprets it as a volume backup (which it is), and reads the desktop-mounted volume "Terabyte" as case-sensitive, as the original volume -- from which the disk image Terabyte.dmg was made -- had been at the time I made it.
"As long as that situation doesn't arise, you should be able to make the copy with a tool that's less fastidious than the Finder, such as cp or rsync."
I'm afraid I have no idea what "cp or rsync" are. I'd be happy to be educated. That's why I came here.
Bart Brown
Message was edited by: Bartbrn
Just trying to unmuddy the water a bit,,,

How can I transfer my iphoto library from a Mac OS Extended (Case-sensitive, Journaled) harddrive to a Mac OS Extended (Journaled) hard drive?

Community,
Every time I try to transfer my iphoto library from a Mac OS Extended (Case-sensitive, Journaled) harddrive to a Mac OS Extended (Journaled) hard drive, I receive the attached message: "You can't copy 'iPhoto Library' because it has the same name as another ideon on the destination volume, and that volume doesn't destinguish between upper- and lowercase letters in filenames."
My theory is, if I am able to unpackage my iphoto library, I can transfer each folder one at a time so that I can trouble shoot any "duplicates." Will this work?
Let's say that works. How can I repackage the library so iphoto recognizes it?
Is there a better way?
Thank you,
Jonathan

Can we assume that I don't have any naming conflicts? Clearly there are or else I wouldn't get the error I'm getting.
The error doesn't mean you have name conflicts. It means that the Finder won't take the chance that you might have them.
You're suggesting that all I would need to do would be to use Carbon Copy Cloner to transfer the files from the case-sensative harddrive to my Extended Journaled harddrive?
Yes. But I would just use the built-in rsync shell command. First, back up all data if you haven't already done so. Launch the Terminal application by entering the first few letters of its name into a Spotlight search. Copy or drag -- do not type -- the line below into the Terminal window, then press the space bar:
rsync -aE --delete
Now drag the iPhoto library you want to copy into the window. You should have something like this:
rsync -aE --delete /Users/you/Pictures/iPhoto\ Library
Drag the Pictures folder on the destination volume into the window. Now you have this (line will wrap on the page):
rsync -aE --delete /Users/you/Pictures/iPhoto\ Library /Volumes/something/Users/you/Pictures
Press return. The copying operation will start. When it finishes, you'll see a new dollar-sign ("$") prompt below what you entered. If there were no errors, you're done.

How can I deal with case-sensitive filenames referred to inconsistently inside other files?

I have downloaded into Dreamweaver an existing web site that I'll be taking over from someone else. The site was built with Microsoft Front Page and apparently now runs on a Windows web server. While redesigning the site, I'd like to upload it to a web server belonging to me, where I can maintain a work in progress that is accessible to others (so they can give me input as I go along). But my site is running on a Unix system, where filenames are case-sensitive.
In the site I've inherited, I've discovered at least one file that is referred to in other files sometimes with one character in upper case and other places in all lower-case. The actual filename contains the upper case character and locally, on my Windows system, it doesn't matter. But on the server the file is not found when it is referenced in all lower-case.
Of course, I can create an all lower-case symlink on my Unix server for the mixed-case file that I know about. But I don't want to look through every file on the site for other files which may vary, case-wise, in how they are referenced. Is there any way that Dreamweaver can help me; for example, by going through and changing all mixed-case filename references inside files, to be consistent with the actual filenames?
I know this is a lot to ask of Dreamweaver and I'm not optimistic. But if anyone knows of a solution, I'd appreciate it.

he means that if you use the file > find function
(on windows this can be called upoon using CTRL + F)
you will be able to go through all the files which are cauing you a problem and change their names so that they are all in the same case
be warned thou
if case sensitivity is your problem,
and
if some code references to your files are written in one case and some are written in the other case, simply changeing the case of the file names will not help.
what you are trying to do will only work if
> ALL of the file names are in one case
or
> ALL of the files names are the same case
bcause this will mean you can change the one which does not always match using CTRL + F
if there is a mix and match on both sides then you are in for a lot of work, if this problem involves multiple names then i would advise you to simply start over!

How do i reformat a case sensitive external hard drive without losing data

I know there are a lot of posts about this, and i have spent hours trying to find a soloution / understand what people have responded to others, but i can't work this out.
I also have a Buffalo HD (let's call it HD1) that stores my itunes library.
I have a WD My Passport for Mac (let's call it HD2) that backs up my Mac Book Pro.
I have an older WD that has older TM back ups on it from previous computers (let's call it HD3)
I have one spare completely 'clean' WD hard drive (let's call it HD4).
My laptop was really slow and full so i went to Genius bar, they sold me the Buffalo HD and they moved my itunes to it and set it up so it now has my itunes. I used this disk to run two TM Backups before i realised the drive was nearly full, so i bought the WD My Passport HD2.
I now use WD My Passprt HD2 for TM.
I want to MOVE the backups on HD1 to My Passport HD2 as there is lots of space on it. I also want to move my itunes library from HD2 as a back up.
But i can't!!!
After reading for hours, apparently this is because my HD1 is case sensitive, journaled. And it needs to be Journaled to work with TM/OSX or something very confusing. I have read lots of threads about re-formatting / partitioning and all things that are way over my head. But the one thing i do understand is if i reformat HD1, it erases the data.
This is NOT an option as it holds my WHOLE itunes. The Itunes is WAY too big to drag onto my mac book pro and then move it over to HD2 and make that my itunes folder.
HOW THE **** ARE YOU SUPPOSED TO BACK UP THE CASE SENSITIVE DRIVE BEFORE REFORMATTING IT IF IT'S TOO BIG TO FIT BACK ON YOUR COMPUTER? Surely that's the whole point of having an external drive... to back up AND give you more space?
I'm so mad that the apple store did this to me... they should know that case sensitve wouldn't work with a passport... that i would have problems. UGh.
I have options to move the files from HD1 as i have HD2 and HD3 and then also the completely unused HD4... but i can't move anything anywhere due to this case sensitive nightmare.
Someone PLEASE HELP ME.
thanks.

Hi Kappy,
Just wondering if you had any advice for my situation . . .
My time machine backup was backing up to a drive that was "Mac OS X Enteded Journaled, Case Sensitive." I had no idea what this meant, or that it would even cause issues.
I took my computer to the Apple store yesterday, and they wiped it clean. When they tried to restore it from the Time Machine backup drive, it would not work. Their guess is that Time Machine cannot restore from a drive that is "case sensitive."
Any thoughts on how I can convert my time machine backup data from a "case sensitive" state, to a "non-case sensitive" state? I've tried to just drag and drop the files from the case sensitive formatted drive to a new drive that I have that is formatted non case sensitive, but I get the following error message:
"The volume has the wrong case sensitivity for a backup"
I just really want my data back - I thought TimeMachine was the way to go (and was supposed to work) but unfortunately it is not.
Any help you can provide would be greatly appreciated.
Thanks,

Why Case-Sensitive while assigning tasks to other users??

I am trying to assign a task to another user through AdminUI.
While searching for users, I am supposed to provide case-sensitive search text to find actual users.
In previous installations it is not a problem. i.e only in production it happens.
Is there any place to modify this settings?
Please see the attached screenshot of the page.
Thanks,
Nith

Raghu,
thanks for the reply, you are right as per the audit .But suppose if it is for 200 users ,creating 200 CUP requests will be impractical right.
there should be some solution for this , because there will be many situations practically where we have to assign roles to N number of users.
Is this possible in GRC 10 ? any idea ?
Regards,
Jaags

Time Machine Case-Sensitive Error

I've read several posts about people who encounter the Time Machine error that arises when TM thinks that one of the volumes (source or destination) is case-sensitive while the other is not. Some people encounter this error genuinely, by which I mean that there is in fact a discrepancy between the file systems; this is not the situation I wish to address.
There are other people - myself included - who have been using TM successfully for months or longer until one day the error crops up. When we check Disk Utility, both source and destination are shown to be case-insensitive. Many approaches have been suggested, from rebooting to reformatting, and many people have reported success; however, it appears to me that the problem has not been solved, since the cause of the problem has not been identified.
In my own experience rebooting sometimes fixes the problems temporarily (for a few weeks) before it later reappears. But I would rather not reboot repeatedly, repeatedly Verify the disks using Disk Utility (finding no errors every time), or reformat unless I am sure that it will fix the problem once and for all. With that in mind, does anyone know of a permanent fix to this problem?
Details:
- TM thinks that the source volume Macintosh HD is case-sensitive
- Disk Utility says that both the source and the external Firewire destination are case-insensitive

Hi, and welcome to the forums.
I've not seen any such posts here (and I read at least the title of every post in both the Leopard and Snow Leopard Time Machine forums).
There are problems, on occasion, when there's a case-sensitive disk image of some kind on the internal HD (some downloaded software comes on case-sensitive disk images, for some reason); but that doesn't seem to be what you're experiencing.
What, exactly, does the message say?
There might be some sort of problem with your internal HD. When this happens, does the disk show it's S.M.A.R.T. status as Verified? Does +Verify Disk+ ever show an error?
I'd be inclined to try a "full reset" per #A4 in the Time Machine - Troubleshooting *User Tip,* also at the top of this forum. It's possible the preference file that directs you to is corrupted. This is a long shot, of course, but worth a try.
If this happens again, look for any disk images, and try to get the exact message. You may also want to look in your system.log for messages.

Case sensitive statement in the select-statement

Hi All,
i have a table in the abap-dictionary filled with names...when i try to select them with the select-statement with condition:
table-name_column like 'some_name'
I have encountered some problems...the inquiry is case-sensitive. What i want to do is to read the value from the abap-dictionary table uppercase or lowercase and compare it with the needed value also translated in uppercase or lowercase.
The only idea i have is to select all values of the dictionary table into an internal table and to translate the values there in uppercase or lowercase and then to loop trough it. But this approach would cost a lot of performance.
Do someone has an other proposal?

check...
Select statement
It would be difficult , because it is based on how data is stored in the data base , now consider the scenario of the system i am using , we can material description as 'test' or 'TEST' , 'Test' .
If in your system there are only stored in either caps or small the you can perform the select twice .
But i myself dont find it to be such a good solution , but you can give it a try
There is one more solution specific to material description ,and that is in the table MAKT there is a field MAKTG , which stored the description in uppercase , so for this you can first convert the description to uppercase and then perform select on this field

CS5.5 Master Collection on Case-Sensitive File System

Hello,
The first thing I'll say is that I already know it's not possible to install on a case-sensitive file system.
So, on to my question. I have been tasked to find out a way to get this installed on our 30-35 Macs with case-sensitive file systems (required for other courses/tasks, so not an option to format.) I was trying to think of a work-around that would let me install and use the CS5.5 Master Collection, but have not been successful yet. Please note, I am not looking for a hack or extensive renaming of a bunch of files or other half-solutions I've found.
Basically, what I was wondering is, if I go into Disk Utility and create a 35GB "Disk Image", mount that, and then try to install, why doesn't that work? I mean, I am technically trying to install to a case-insensitive file system at that point, but CS5.5 still pops up with an error. Has anyone gotten this type of solution to work, or any other for that matter? Luckily my college hasn't bought the licenses for all these systems yet, but when a solution is found, they're jumping on it right away. The main reason I don't want a "hacky" solution is that being deployed on 30-35 systems, this has to be a simple solution, not something that takes hours per system.
Any insight is greatly appreciated.
Jeffrey Simmons

Thank you for the information, I had a hunch it was installing stuff elsewhere too, but wasn't 100% sure. As for the problem, I ended up just converting to a case-insensitive boot partition. To others who may want to do this, I used iPartition without a problem. The only catch is, you can't just run it from the OS drive, you either have to burn a iPartition Boot DVD (requires you have your OS dvd as well), or do what I did and just install OSX to an external drive, install iPartition, then convert the file system on the regular OS drive. A bit of a hassle, but you don't have to format your system.
CS5.5 Master Collection then installed fine, with no problems. Unfortunately, Photoshop keeps repeatedly crashing. It's fine for hours, then crashes 4+ times within an hour. Repeats this over and over unfortunately. Adobe support hasn't been helpful at all, so I'm just going to return this software and continue using Gimp. It has always done everything I wanted, but I wanted the "name brand" software. In the end, it's not worth the hassle, and definitely not worth losing my work over and over, so back to the store it goes. Thanks again for taking the time to help out though.
Jeffrey Simmons

How to get Case Sensitive Check Box at Search Page

Hi Everyone,
I am trying to get case sensitive check box at the bottom of the search page, for that we have to set any propert or we ahve to do anything else.
Please Help!!!!
Thanks,
Amit

Have never really thought of it. One thing you need to do is set the Case Insesitive Searching Option correclty in PeopleTools Options. I can't find any other setings. But it might have to do with the fields that are on your Search record. My guess is if any of the Search Fields are of type Character and format Mixedcase then the Case Sensitive check box will be displayed automatically.

BUG - FTP with case sensitive server

My provider uses case sensitive file and directory names. I
created a directory 'OtherStuff' on the server directly (not from
remote view). In Dreamweaver's FTP setup I erred by specifying the
subdirectory of 'otherstuff'. When I created a default html file
and PUT it, FTP failed to find the directory but continued and put
the default html file in the root, overwriting my default web file.
Yes, I erred. However, it would be good if Dreamweaver would
stop when it encounters a cd failure.

jjstafford wrote:
> My provider uses case sensitive file and directory
names. I created a
> directory 'OtherStuff' on the server directly (not from
remote view). In
> Dreamweaver's FTP setup I erred by specifying the
subdirectory of 'otherstuff'.
> When I created a default html file and PUT it, FTP
failed to find the
> directory but continued and put the default html file in
the root, overwriting
> my default web file.
>
> Yes, I erred. However, it would be good if Dreamweaver
would stop when it
> encounters a cd failure.
>
>
You can enable case sensitive link checking in the site
manager.
However, this is more the issue of the OS, rather then DW.
Windows -
which is the OS you use, I assume - is about the only OS
(that I know
of) which is case insensitive!
All Linux/Unix based servers are case sensitive.

Copying folders & files from case-sensitive to non-case-sensitive volume

I'm trying to copy a rather large (60+ GB), folder and all its enclosed items from a volume that is has case sensitive file names to one that does not. The copy operation always stops when it comes across a duplicate file/folder name differing only in the case of some of the characters. The folders/files in question are actually not duplicates, so I would like to change the file name of the duplicate by appending anything to the filename.
The copy operation does not provide any choice but to abort the operation when it finds the first identical file or folder name differing only in case..
Any suggestions?

Unfortunately, that is not a viable solution, as I am tring to convert a case sensitive volume to a non-case sensitive volume.
What I would like is a method to copy files and when a duplicate occurs it asks me what to do like rename the second duplicate. However this problem is now moot, as I painstakingly renamed each offending file/folder as each error occured, and then restarted the copy.
While the question is not answered, I am marking it as such because I am now past the problem.
Thanks for your response.

Problems retrieving backup from Time Machine, Case-sensitive HD

Hello.
I'm trying to manually retrieve the information I got in a Time Machine, but for some reason I kept getting an error saying that there were files that were going to the same location were named in the same way. After checking a couple of things I noticed that, somehow, the external HD was Case-sensitive, so I'm assuming that, instead of +File, File 01 File 02+ it's sorted out like +File, file, filE+, and since the computer's HD is normal it's having a conflict with those file names.
That being said, is there a way to fix this? What I'm trying to move is an iTunes and iPhoto Library, "probably" iTunes could be done manually, but in iPhoto there's over 10 GB of pictures and I'd probably take a looooong while to fix it manually.
Any work around?
Thanks!

Hi Adrian ...
Let me see if I can help ...
I'm trying to manually retrieve the information I got in a Time Machine, ...
How? With the TM App or from the Finder?
but for some reason I kept getting an error saying that there were files that were going to the same location were named in the same way.
It's just letting you know that the original file, on the System HD, still exists and wants your permission to over write the original file with the TM file. Backing up your System HD to TM should not have changed any of the original file names. If TM had changed the Case when backing up from your System then TM Restore would have duplicate these files/folders without even asking you.
That being said, is there a way to fix this?
Yes. After you have restored the files/folders that you want to keep you can reformat the TM HD. Or try one of my tricks which is to just reformat the free space. Use the Mac OS X Extended (Journaled).
Good Luck.
Buzz

Case Sensitivity in "Find"

Similar Messages

Maybe you are looking for