Case Sensitive Check

Hi,
Is there any way, java could differentiate case sensitive file names or folder names on a windows machine, i think its possible on a linux box. can anyone help me on this
thanx

Java on windows and Java on Linux are the same. The operating systems on the other hand are not: windows is case insensitive and Linux is case sensitive. So there is no need to differentiate case sensitive filenames on windows as you cannot have two files with the same name in the same folder.

Similar Messages

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.

Case-sensitive search for equipments

Hello gurus,
when looking for certain equipments using F4 (program RIEQUI20), I can search for all equipments of a certain manufacturer (field HERST).
Unfortunatelly this search is always case-sensitive, i.e when I enter "BOSCH", equipments with manufacturer "Bosch" are not found and vice versa.
Is there any way to change this behaviour?
Thanks in advance
Alicia

Alicia,
Oops ..Sorry about that. I had misread it. You will not be able to accomplish the same in standard enhancement.You could remove the case sensitive check box on the HERST data element.But that would be considered A modification.That might however do the trick and save all the new contents in CAPS.The search help will then pick everything.(You may have to go into change mode on existing records and re save them for this change to be updated in DB )
However you could achieve the same, without modification and with a little bit of custom development.
What you could do is, create a Custom elementary search help(SE11) with the standard fields HERST(Input) and EQUNR(Output) fields .Create and Attach a custom Search help exit to the same by copying F4IF_SHLP_EXIT_EXAMPLE. In here modify the STEP SELECT to append a translated (Upper and lower case) selection condition to the query or a appropriate wild card search.Then select the same from EQUI.This should pull all your records. After testing this out , append this search help to the standard collective search help EQUI.
Hope this helps.
Regards
Narasimhan
Edited by: Narasimhan Venugopal on Jan 7, 2010 10:24 AM

Can we ignore the case-sensitivity

Suppose my table has a column of varchar datatype and I have inserted data in uppercase or lowercase or in mixed case.
If I want to fire select query then I'll have to take care of the case.Is there any way so that we can ignore the case sensitivity of the database and we can fire select queries without considering case of the data?
In other words,
Is there is any option available in Oracle to bypass case sensitive configuration while retrieving output from oracle query. Oracle does not return output if data in table are in capital letters and query to retrieve data contains value in title case or lower case.An option to deal with such case is to use upper function in oracle query however would be more interested in knowing if there is any option available in oracle to bypass the case sensitive check while retrieving output from query, as it works with SQL.

There're some bugs associated with putting NLS_COMP=LINGUISTICS and NLS_SORT=BINARY_CI
The metalink note id says something about these bugs:
Doc ID:Note:5252496.8
Doc ID:Note:3945156.8
Doc ID:Note:4996004.8
Doc ID:Note:5464341.8
Doc ID:Note:5718815.8

Check Case sensitive values

A field value is coming in caps.
lf_tmp = u2018RMu2019.
I have to check this with another field lf_werks ,which always comes in small letters.
if lf_tmp   CN lf_werks .
    MESSAGE e002(zm) WITH 'The Path is wrong for the plant'
                           p_werks.
ENDIF.
This check always fails even if the values are like belowu2026
lf_tmp = u2018RMu2019.
lf_werks = u2018rmu2019.
How do I by-pass this case sensitiveness u2026.when I want to do the check.
thanks in advance

Actually, I'd do it the other way:
TRANSLATE lf_werks to UPPER CASE.
Since lf_werks can be a combination of upper and lower case, translating lf_tmp to lower case may not always work. This way you are always comparing upper case to upper case.
Rob

Get case sensitive spell check to flag rg174

Here are some words that have been added to spelling dictionary:
CD
CDs
FS237E
George
MS417D
RG174
and also many other product numbers that our company wants to follow our capitalization rules.
For the following sentence:
You might find what george has to present in download format on fs237e, but if you prefer cd format then you should consider ms417D.
Case sensitive spell chcek of this sentence only flags "george" and "cd" as misspellings. but not the two products.
Hopefully Indesign can handle this and simply I am doing something wrong.
Thanks, Edward

I was hoping somebody who actually uses spell checking would pick this up overnight...
I suspect that the problem is ID ignores words with numbers, and I don't see any settings to make that a user choice. You might want to add these to the auto-correct list (smething else I never use).

Check links as case sensitive

I can't remember, and I don't have dreamweaver right now (I'm on vacation):
Does DW support check links site wide as case sensitive?
e.g. does it recognize the difference between ../Images/myImage.gif and ../images/myimage.gif?
or, is there an option to enable/disable that kind of check?

I trust you, and I vote as the right answer, before I even
see it with my own eyes
Thank you Murray

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 do I move my large iTunes collection from a case-sensitive hard drive to a case-insensitive hard drive?

I currently keep my iTunes media on an external hard drive because it takes up too much space on my machine. I recently discovered that it was formatted as case-sensitive when I bought it, and now months later I'm having issues. When attempting to back up my files on a case-insensitive hard drive, the operation failed due to conflicting file/folder names (Artist and artist are now considered the same file name and one would have to overwrite the other). I now have a large iTunes file collection that is stuck on the case-sensitive hard drive, and I want to save a backup on a case-insensitive drive.
Is there a way to identify all cases where multiple files/folders have the same title/album/artist but different spelling so there will be no conflicts? The folder/file names would have to be crossed referenced to highlight any cases where File/fiLe/file would cause a problem.
I imagine there is a way to do this using iTunes script or Automator or a command in terminal or something rather than going through and checking/fixing all the information for thousands of songs by hand. I'm at the limits of my minimal development skills, so any help would be appreciated.

You should be able to use either "Carbon Copy Cloner" or "SuperDuper" (free for this purpose) to copy your case-sensitive volume to an empty case-insensitive one. Make at least two such copies on different drives. One is not enough to be safe.
If there are any name conflicts—that is, files in the same folder with names that differ only in case, such as "File" and "file"—then you will either get an error or one of the files won't be copied. You must ensure either that no such conflicts exist, or that the consequences are not important. How you do that is up to you. Unless you went out of your way to create conflicts, they probably don't exist.
Then erase the source volume in Disk Utility as case-insensitive. This action will remove all data from the volume.
Restore from one of your backups using the same application you used to create it, or use the "Restore" feature of Disk Utility, which will be faster. Search its built-in help for the term "duplicate" if you need instructions.

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.

Problem in XI - JDBC (oracle) Scenario, case sensitive column name

I had a XI -> JDBC scenario, connecting to a SQL server, where the query was being generated using Message Mapping (XML SQL Format),
now the database has been migrated from SQL server to Oracle, and we are using the same XI scenario, but now the problem is, the query generated using message mapping doesnt work because it seems the query (UPDATE statement) requires the field name as having All capital letters, i mean the Column name in query to Oracle has become case sensitive,
can u help me out

Hi
Oracle doesnt have restriction that Query has to be in uppercase for any column. But it is good go use Upper case for the Query.
Use oracle editor to do the query if it is working fine and then use XML SQL in XI
Check this thread SAP has given some
http://help.sap.com/saphelp_nw04s/helpdata/en/43/68a541a1166153e10000000a1553f6/frameset.htm
Check FAQ on the JDBC adapter, see SAP Note 831162
always useful Note
Thanks
Gaurav

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

Are idoc fields case sensitive?

Hello, there has been an error during idoc processing. The trading partner field was filled in lowercase and this is bringing me error Message no. FB279 ' Company dp0017 is not defined'. The other idocs had DP0017 filled in and were processed fine.
Any input on this? thx.
Edited by: Antish Awootar on Jun 7, 2011 8:02 AM

Hi Antish,
It actually depends on the value that is stored in the IDOC, if the IDOC has company code in lower case then that is exactly how it will be used in the program for all purpose and no automatic conversion is applied. The below message is thrown in the FM - FI_COMPANY_CHECK This FM will look up the table T880 - If you check the entry in this table will be DP0017 and not dp0017. Hence it is throwing the error message.
If your question is it works fine when i try in SE37 with the FM "FI_COMPANY_CHECK" or if i input "dp0017" in WE19 or in SE11 against T880, then the reason for that is a conversion is applied automatically and it is changed to DP0017.
To answer your question "Are idoc fields case sensitive?", it depends on the context, does it retain the case when it is filled in, yes it does.
Regards,
Chen
Edited by: Chen K V on Jun 7, 2011 4:10 PM

Case-Sensitive File System?

I downloaded the trial for Flash CS4 pro and it won't install on my computer.
It says:
System Requirements Error
This software cannot be installed because the file system of the OS volume is not supported. The OS volume should be local , writable and should have non case-sensitive file system
Anything I can do to get it to work? I have a MBP running Leopard on an intel processor.
Message was edited by: guynjoan

guynjoan wrote:
The hard drive is internal. And Adobe tech doesn't work on the weekends. I checked the "get info" on my hd and it said it is case-sensitive,
that's your problem. Lots of apps have problems with case sensitive drives so you should never use case sensitive file system unless you have a compelling reason to do so. Your only recourse now is to move your data to a non case sensitive drive. Clone your hard drive to an external drive, boot from the leopard install DVD, reformat the drive non case sensitive and install leopard on it. then use migration assistant to migrate your data from the external.

Case sensitive Tag names

Hi friends
I have a question, is it possible to transfer case sensitive tag names into xml structure ? for exemple, I want to transfer Tag name "DateCreated" . I did a test but start tag names is "DataCreated" and it is Translated in "DATACREATED" and this is a problem.
Thanks
Sergio

Sergio,
Usually what ever you have given in your xsd or message type you will have the same. So please check it. I just tested this and it seems to be the same as defined in your xsd or message type.
Regards,
---Satish

Case Sensitive Check

Similar Messages

Maybe you are looking for