Convert mixed case value in colum into upper case values

Hi All,
I have got a table call emp and has the following colums:
id number 10
suename_name varchar2(20)
given_name varchar2(20)
position varchar2(30)
date_hired date
Now the values in colums are mixed case and I need to change them to upper case. I think I need to use upper function to do it.
Could anyone help me by providing me sql/pl sql script to through each colum in emp table and change them to the upper case.
Many Thanks
Michael

Hi,
If you really want to try this using PL/SQL, then you'll have to use dynamic SQL, something like this untested code, since the table and column names are vaiable:
SET   SERVEROUTPUT  ON  SIZE 50000
DECLARE
     sql_txt     VARCHAR2 (4000);
BEGIN
     FOR  r  IN ( SELECT  table_name
               ,       column_name
               FROM    user_tab_columns
               WHERE   data_type = 'VARCHAR2'
          --   AND     ...  -- if you don't want all columns in all tables
     LOOP
          sql_txt := 'UPDATE "'
               || r.table_name
               || '" SET "'
               || r.column_name
               || '" = UPPER ("'
               || r.column_name
               || '")';
          dbms_output.put_line (sql_txt || ' = sql_txt');     -- For debugging
          -- EXECUTE IMMEDIATE sql_txt;               -- For real
     END LOOP;
END;Dynamic SQL (here) means creating a string that contains the SQL statement to be done, then using EXECUTE IMMEDIATE to run it.
Whenever you write dynamic SQL, it's a good idea to only display the SQL statement during the early stages of debugging. When it's displaying correctly, then you can try un-commenting the EXECUTE IMMEDIATE line.
Edited by: Frank Kulash on Jul 19, 2009 4:40 PM
A little more complicated, but a lot more efficient:
SET   SERVEROUTPUT  ON  SIZE 50000
DECLARE
     sql_txt          VARCHAR2 (4000);
BEGIN
     FOR  r  IN ( SELECT    table_name
               ,         column_name
               ,         ROW_NUMBER () OVER ( PARTITION BY  table_name
                                  ORDER BY       column_name
                                )     AS column_num
               ,            COUNT (1)     OVER ( PARTITION BY  table_name
                                )     AS total_column_cnt
               FROM      user_tab_columns
               WHERE     data_type = 'VARCHAR2'
          --   AND       ...  -- if you don't want all columns in all tables
               ORDER BY  table_name
               ,            column_name
     LOOP
          IF  r.column_num = 1
          THEN
               sql_txt := 'UPDATE "'
               || r.table_name
               || '" SET "';
          ELSE
               sql_txt := sql_txt || ', "';
          END IF;
          sql_txt := sql_txt ||
               || r.column_name
               || '" = UPPER ("'
               || r.column_name
               || '")';
          IF  r.column_num = r.total_column_cnt
          THEN     -- This is the last row for this table; run it
               dbms_output.put_line (sql_txt || ' = sql_txt');     -- For debugging
               -- EXECUTE IMMEDIATE sql_txt;               -- For real
          END IF;
     END LOOP;
END;
{code}
The difference is that the first solution produces and executes a separate UPDATE statement for each column, like this:
{code}
UPDATE "TABLE_1" SET "COLUMN_A" = UPPER ("COLUMN_A");
UPDATE "TABLE_1" SET "COLUMN_B" = UPPER ("COLUMN_B");
UPDATE "TABLE_1" SET "COLUMN_C" = UPPER ("COLUMN_C");
{code}
but it's much more efficient to do change all the columns at once, as long as you have the row in hand.  So the second solution only creates one SQL statement per table, like this:
{code}
UPDATE "TABLE_1" SET "COLUMN_A" = UPPER ("COLUMN_A")
           ,   "COLUMN_B" = UPPER ("COLUMN_B")
           ,   "COLUMN_C" = UPPER ("COLUMN_C");
{code} where every line above corresponds to a row fom the query.  The first line for every table will start with
{code}
UPDATE "TABLE_1" SET "but all the others will start with
{code}
and only on the last column for a given table will the statement be executed.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

Similar Messages

  • Converting mixed case table name to upper case

    I am migrating data from Access to Oracle and new tables and columns being created are in mixed case is there a way to convert all tablename or column name automatically.
    Also does the migration workbench handle the memo fields currently defined in my oracle database.

    If you want tables and columns to be created in Upper Case then make sure the Create ANSI-Compliance Names checkbox is unchecked in the options section.
    1.Open Workbench.
    2.Tools -> Options
    Memo fields are migrated to CLOB fields in Oracle.

  • Problem in converting into upper case urgent

    hi,
    i  working on module pool program.
    in the initial screen there is two fields one is number one is name.
    if i enter the name in the name field it is automatically converting into upper case,
    but in this case my select query is not working,how to solve this,i mean i have to take same as it is what i entered.
    kindly give me suggestion.it is urgent issue.i have to delever today.
    Thanks,
    mohan.

    hi
    in the Report to handle like this situation.. we use the extentions to the parameter  as  LOWER CASE .
    parameters p_t type char10 LOWER CASE .
    i think in the Module pool also.. we can do this in Properties of the FIELD... once check the Properties of the field... there  could be a chance.
    hi
    <b>there is field <b>checkbox called UPPER/LOWER CASE</b>at the bottom of the properties... if tick this u r porblem will be solved</b>
    Please Close this thread.. when u r problem is solved
    Reward if Helpful
    Regards
    Naresh Reddy K
    Message was edited by:
            Naresh Reddy

  • Convert data in table to mix case

    Hi All,
    I have a table that contains data.
    This table has to columns, an id and description.
    I would like to update my table to convert data to mix case.
    As of now, all of my data in the table are lower case.
    What I mean by mix case is first letter for each word is uppercase and the rest are lower case.
    is there a function i can use ?
    example:
    Amended/Resentence, Type UnknownThanks

    You can use the INITCAP function.
    update table
    set description = INITCAP(description);Example:
    create table test (description varchar(50));
    Table created
    insert into test values ('amended/resentence, type unknown');
    1 row inserted
    select * from test;
    DESCRIPTION
    amended/resentence, type unknown
    update test set description = initcap(description);
    1 row updated
    select * from test;
    DESCRIPTION
    Amended/Resentence, Type Unknown

  • RE: Converting to mixed case.

    >
    I recall seeing a method that would convert all upper or all lower case to
    mixed case. Does this sound familiar to anyone?
    Hello Everyone
    I've developed a single Domain Class to support this behavior. With this
    Domain Class you can choice to convert to mixed case each word of the
    text or only the initial word and the word after a period by setting the
    value of the ToUpdateEachWord attribute (boolean).
    Here is an example of this domain class.
    I hope this help you.
    Victor Navarro
    [email protected]

    we have a database which I want to use as the source for generating a Java API, and I need/want the Java classes and attributes to be (automatically) created with mixed case names. At the same time we have existing applications and scripts that access the database, and these assume case insensitive table and column names.Not sure if I got you right, but how about creating views as e.g in
    SQL> create or replace view "Dept"
      2  as
      3     select deptno "Deptno", dname "Dname", loc "Loc" from dept
      4  /
    View created.This will allow you to continue to query in case insensitive manner as well as case sensitive:
    SQL>
    SQL> select * from dept
      2  /
             DEPTNO DNAME          LOC
                 10 ACCOUNTING     NEW YORK
                 20 RESEARCH       DALLAS
                 30 SALES          CHICAGO
                 40 OPERATIONS     BOSTON
    SQL> select * from "Dept"
      2  /
             Deptno Dname          Loc
                 10 ACCOUNTING     NEW YORK
                 20 RESEARCH       DALLAS
                 30 SALES          CHICAGO
                 40 OPERATIONS     BOSTON
    SQL>As I understand, you could use the views (instead of the tables) to automatically generate mixed case classes while continuing to have case insensitve queries?!

  • How to convert lower case to upper case?

    Hi,
    How to convert lower case letter to upper case and vice versa?

    TRANSLATE
    Variants:
    1. TRANSLATE c TO UPPER CASE.
    2. TRANSLATE c TO LOWER CASE.
    3. TRANSLATE c USING r.
    See String processing
    Variant 1
    TRANSLATE c TO UPPER CASE.
    Variant 2
    TRANSLATE c TO LOWER CASE.
    Effect
    The first variant converts all lowercase letters in c to uppercase. The second variant converts all uppercase letters to lowercase.
    Example
    DATA letters(3) TYPE C.
    MOVE 'abc' TO letters.
    TRANSLATE letters TO UPPER CASE.
    letters now has the contents 'ABC'.
    Note
    The classification of upper- and lowercase, and the actual characters used are determined by the current text environment (see SET LOCALE LANGUAGE). Problems may occur when the system converts the characters, if the wrong language has been specified in SET LOCALE LANGUAGE, or if data has been processed that does
    Variant 3
    TRANSLATE c USING r.
    Effect
    Replaces all the characters in the field c according to the rule in field r. c1 containscharacter pairs. The second character in each pair replaces the first. If r does not contain a character in c, this character remains unchanged. r can also be a variable.
    Example
    DATA: letters(20) TYPE C VALUE 'abcabcabcXab',
          change(15)  TYPE C VALUE 'aXbaYBabZacZ'.
    TRANSLATE letters USING change.
    letters now contains 'XaZXaZXaZXXaZ'.
    REWARD IF USEFUL

  • Converting to mixed case.

    I recall seeing a method that would convert all upper or all lower case to
    mixed case. Does this sound familiar to anyone?

    Try using this formula
    propercase(split(,"-")[2])
    Regards,
    Raghavendra

  • How to convert lower case letter to upper case letters

    hai all,
    How to convert lower case letter to upper case letters??
    Thanks & Regards,
    suresh

    Hi Suresh,
    Include ALL_CAPITAL in the RSKC Tx.
    Also try this code in your Transfer rule,
    TRANSLATE TRAN_STRUCTURE-(Info Object Name) TO UPPER CASE.
    RESULT = TRAN_STRUCTURE-(Info Object Name)
    Hope this solves................

  • I need to tanslate a field into upper case

    Hello :
    i would like to ask one favor i am trying to make a selections of data.
    i have a RFC function that recieve a parameter and this parameter is used in selection of data.
    for example when i send the parameter i transalate this into upper case using TRANSALATE VARIABLE TO UPPER CASE, so when i make the selections of the information i found all those data that also have upper case information in this field , but when one of that fields doesn't have upper case i can't find the information.
    The problem is that the table has both information upper-lower case.
    if somebody knows how to fix this problem i will appreciate .

    One way to handle this if you can't control how the data is entered and the table is not too big, is to get all of the data into an internal table, translate the variable, then loop at the internal table and translate the field that you want to compare to upper case, then do the comparison, if not satisfied, then delete it from the internal table.
    Translate v_parm to upper case.
    select * into table itab from ztable.
    loop at itab.
      translate itab-fld1 to upper case.
        if v_parm <> itab-fld1.
          delete itab.
          continue.
        endif.
    endloop.
    Regards,
    Rich Heilman

  • Need to convert a binary value into decimal

    Hi i need to convert a binary value which i would be getting as a string object to a decimal value......need code for the same

    Check Integer.parseInt
    http://java.sun.com/j2se/1.5.0/docs/api/java/lang/Integer.html#parseInt(java.lang.String,%20int)

  • Generating mixed case for table and column names

    I trying to get table definition from Oracle 9i database into my toplink workbench
    (version 9.0.3), the column names and table names are capitilized by
    default, how do I change this to be mixed case? Thanks

    I'm not sure why you want them changed. The Oracle database by default is case insensitive, which in essence means it converts everything to upper case when a case is not specified (which can be done by wrapping it in quotes). Unfortunately, Java strings are case sensitive. This means that if you try searching resultsets for "TableName" when the database driver is returning "TABLENAME", you will run into problems. It is probably better to have your project match your database as closely as possible to avoid any issues later on.
    That said, I don't know of a way to automatically have the workbench use mixed case names - it uses the strings as they are returned from the database. I believe you will need to manually change the table names if you want them to be different than what you have imported.
    Best Regards,
    Chris

  • Fetching data from database in case of mixed case in SE37

    Hi,
    I have created a function module(in se37) where the input is Last name(PA0002-NACHN). My requirement is i have to fetch data from PA0002 based on last name. But the problem is if i give a name in mixed case(both upper and lower) sap converts the last name into Capital letter and starts searching the database.
                      But i tried in abap editor. here SAP accept the parameter(last name) as mixed case and starts searching. Why in function module the parameters are converted into upper case. How to restrict it.
                 If i will create a domain with LOWER CASE check box checked and try to call the dataelement in import part of function module then also it's converting it inot upper case. If i uncheck the lower case check box then also it's taking it as upper case.
                How to process the input parameter in function module(SE37) which should take the input as user enters,i.e if user enters small letter it should take it as small letter , if mixed letter it should take it as mixed letter and start searching.
    regards
    sandeep

    HI sandeep,
    <i>"If i will create a domain with LOWER CASE check box checked and try to call the dataelement in import part of function module then also it's converting it inot upper case. If i uncheck the lower case check box then also it's taking it as upper case."</i>
    I think the data is getting converted to upper case even before it is passed to this FM.
    Can yo ushow how are you testing this FM?
    If you are calling this FM in a abap program using a parameter, it will convert the text to upper case as and when you enter data the name in it.
    Regards,
    Ravi

  • To Convert the Case

    Hi,
    i am using the function module to get the amount in words,
    CALL FUNCTION 'HR_IN_CHG_INR_WRDS'
      EXPORTING
        AMT_IN_NUM               = TOT
    IMPORTING
       AMT_IN_WORDS             = WA_SPELL
    EXCEPTIONS
      DATA_TYPE_MISMATCH       = 1
      OTHERS                   = 2
    but the problem is i get the amount in capital letters
    for ex : ONE LAKH TWO Rupees
    but i need the o/p in form
    ex: One Lakh two RUPEES
    how can i convert the case...
    kindly help

    For case translation :
    TRANSLATE
    Variants:
    1. TRANSLATE c TO UPPER CASE.
    2. TRANSLATE c TO LOWER CASE.
    3. TRANSLATE c USING r.
    4. TRANSLATE c ...FROM CODE PAGE g1...     TO CODE PAGE g2.
    5. TRANSLATE f ...FROM NUMBER FORMAT n1... TO NUMBER FORMAT n2.
    Depending on whether byte or character string processing is carried out, the operands can only be byte-type or character-type (see Overview).
    The syntax check performed in an ABAP Objects context is stricter than in other ABAP areas. See Only character-type fields allowed in string processing.
    In some cases, the syntax rules that apply to Unicode programs are different than those for non-Unicode programs.
    See String processing
    Variant 1
    TRANSLATE c TO UPPER CASE.
    Variant 2
    TRANSLATE c TO LOWER CASE.
    Effect
    The first variant converts all lowercase letters in c to uppercase. The second variant converts all uppercase letters to lowercase.
    Example
    DATA letters(3) TYPE C.
    MOVE 'abc' TO letters.
    TRANSLATE letters TO UPPER CASE.
    letters now has the contents 'ABC'.
    Note
    The classification of upper- and lowercase, and the actual characters used are determined by the current text environment (see SET LOCALE LANGUAGE). Problems may occur when the system converts the characters, if the wrong language has been specified in SET LOCALE LANGUAGE, or if data has been processed that does
    Variant 3
    TRANSLATE c USING r.
    Effect
    Replaces all the characters in the field c according to the rule in field r. c1 containscharacter pairs. The second character in each pair replaces the first. If r does not contain a character in c, this character remains unchanged. r can also be a variable.
    Example
    DATA: letters(20) TYPE C VALUE 'abcabcabcXab',
          change(15)  TYPE C VALUE 'aXbaYBabZacZ'.
    TRANSLATE letters USING change.
    letters now contains 'XaZXaZXaZXXaZ'.
    Variant 4
    TRANSLATE c ...FROM CODE PAGE g1 ...TO CODE PAGE g2.
    Parts marked with " ..." are interchangeable
    TRANSLATE c TO   CODE PAGE g2.
    TRANSLATE c FROM CODE PAGE g1.
    Instead you can use conversion classes.
    Effect
    Converts the contents of the field c from character set g1 to character set g2. This variant uses the conversion table g1 to determine the SAP character, which is then used to determine the new character from g2.
    Transaction SPAD allows you to display and maintain character sets. If one of the conversion tables does not exist, the runtime error CONVERSION_CODEPAGE_UNKNOWN occurs. Conversion combinations that are maintained as part of the runtime system for performance reasons do not trigger runtime errors, and you cannot change them using Transaction SPAD.
    Example
    DATA c(72) TYPE C.
    TRANSLATE c FROM CODE PAGE '1110' TO CODE PAGE '0100'.
    This statement converts the contents of field c from the HP-UX character set to IBM EBCDIC.
    Note
    Fields with types I, P, F, and X remain unchanged by the conversion. The syntax check only allows character fields for specifying the codepage. However, since the codepage is maintained in table TCP00 as a type N field with length 4, you should use this type.
    Variant 5
    TRANSLATE f ...FROM NUMBER FORMAT n1 ...TO NUMBER FORMAT n2.
    Parts marked with " ..." are interchangeable
    TRANSLATE f TO NUMBER FORMAT n1.
    TRANSLATE f FROM NUMBER FORMAT n1.
    Instead you can use conversion classes.
    Effect
    Converts the number formats in f. Currently, the number formats '0000' (HP, SINIX, IBM) and '0101' (DEC-alpha OSF) are supported. Other formats trigger the runtime error TRANSLATE_WRONG_NUM_FORMAT . If you omit FROM NUMBER FORMAT or TO NUMBER FORMAT, the system uses the system number format.
    Example
    DATA: f TYPE F,
          hex(2) TYPE X,
          nform LIKE tcp00-cpcodepage.
    The contents of fields hex and f are stored in /ARCHIV
    from another platform. hex is stored in a valid number
    form when it is saved, and can therefore be read on
    all platforms.
    READ DATASET '/ARCHIV' INTO hex.
    READ DATASET '/ARCHIV' INTO f.
    nform = hex.  "Conversion from non-host-specific. HEX into N(4)
    TRANSLATE f FROM NUMBER FORMAT nform.
    Effect
    Converts the contents of f from the nform format of a given platform into the system representation.
    Note
    This converts fields with types I and F. As in variant 4, you should define the number formats with type N and length 4.
    You can display system codepage and number formats using the function module SYSTEM_FORMAT. This allows you to store additional information for archiving purposes.
    Note
    Performance:
    Converting lowercase letters to uppercase (or the other way round) in a 10 byte character field requires around 7 msn (standardized microseconds).
    If you use ... c USING c1... to replace two characters of a 10 byte character field,the runtime is around 9 msn.

  • Issue with mix case

    Hi!
    Is there any way to prevent the data to be converted to upper-case without changing it's domain?
    I'm trying to insert mix case in a CHAR40 domain, but the text allways returns as upper-case.
    Regards,
    Andre

    AMadeira wrote:
    > It is possible to do that using code only?
    Please give more details: what you want to do programatically. ?
    If you check the domain of CHAR40 thru SE11 you can find :lowercase" check box not checked. so it convert to upper case

  • BUG: Export DDL and Data fails for mixed case table/column names

    Hi there,
    I have found a bug in SQL Developer. See details below.
    Description:
    When "Export DDL and Data) function is used on a table/columns not named in UPPERCASE, sql generated by SQL Developer is invalid.
    Steps to reproduce:
    - open SQL Developer, connect to DB
    - make a table named "lowerCase" (in double quotes, so it won't be automatically changed to capital letters)
    - you may also add some columns, for example "lowerCol1", "UpCol2", ALLUPCOL3
    - add some data rows to the table
    - choose Tools -> Export DDL and Data
    - check exporting of tables and data, on "filter" tabs choose your "lowerCase" table
    - press "Apply"
    Error:
    Generated SQL contains invalid INSERTs: mixed-case table and columns are referenced without obligatory double quotes, which yields an error when generated script is executed (see below, relevant line is underlined)
    -- DDL for Table lowerCase
    CREATE TABLE "DBO_HT"."lowerCase"
    (     "lowerCol1" VARCHAR2(100),
         "UpCol2" VARCHAR2(100),
         "ALLUPCOL3" VARCHAR2(100)
    -- DATA FOR TABLE lowerCase
    -- FILTER = none used
    -- INSERTING into lowerCase
    Insert into lowerCase (lowerCol1,UpCol2,ALLUPCOL3) values ('lc','uc','auc');
    -- END DATA FOR TABLE lowerCase
    Remarks
    SQL Developer: version 1.2.1, build MAIN-32.13
    Oracle DBs: 9.2 & Express
    OS: Windows 2000 Professional
    If you need any more details/testing, let me know. I'd really appreciate a quick patch for this issue...
    Alternatively, do you know of any other simple way of copying a single database (it's called a schema in Oracle, right?) from one computer to another? Possibly something so simple like detaching->copying->reattaching mdf (data) files in SQL Server... I thought that this "Export DDL&Data" function will do, but as you can see I couldn't use it.
    I just need a simple solution that works - one operation on source to stuff, get the resulting files to other computer and one operation to have it running there... I think that such scenario is very basic, yet I just can't achieve it and I am simply not allowed to spend more time on it (read: our test project fails, my company rejects my "lobbying" and stays with MSSQL :/ )
    Thanks a lot & bye

    Thanks for your reply.
    ad. 1)
    You're right. I just wanted to give some very short feedback on my experiences with SQL Developer, so I didn't think starting new threads would be necessary, but as I was writing it became much bigger than I initially planned - sorry about that. I will make proper threads as soon as possible. Having "Edit post" button on this forum would also be useful.
    ad. 2)
    Generally, you're right - in most cases it's true that "switching DBMS is a major commitment" and "you will produce terrible code" if you don't learn the new one.
    However, I think that you miss one part of market here - the market that I think Express is also targeted on. I'd call it a "fire&forget databases" market; MySQL comes to mind as possibly most common solution here. It's the rather small systems, possibly web-accessed, whose data-throughput requirements are rather modest; the point is to store data at all, and not necesarily in fastest way, because given the amount of data that is used, even on low-end hardware it will work well enough. What's important here is its general ease of use - how easy is to set up such system, connect and access data, develop a software using it, how much maintenance is needed, how easy this maintenance is, how easy are the most common development tasks as creating a DB, moving a DB from test to production server etc. There, "how easy" directly translates to "how much time we need to set it up", which translates to "how much will the development will cost".
    Considering the current technology, switching the DBMS in such systems is not necesarily a major commitment and believe me that you will not produce terrible code. In many cases it's as simple as changing a switch in your ORM toolkit: hibernate.dialect = Hibernate.Dialect.OracleDialect vs MySQLDialect vs MsSql2005Dialect
    Therefore, in some part of market it's easy to switch DBMS, even on project-by-project basis. The reason to switch will appear when other DBMS makes life easier => development faster. From that point of view, I can understand my colleagues giving me an embarassing look and saying "come on, I won't read all these docs just to have db copied to test server". And it doesn't mean "they are not willing to learn anything new", it's just that they feel such basic task should have self-explaining solution that doesn't require mastering any special knowledge. And if they get such simple solutions somewhere else, it costs them nothing to change the hibernate dialect.
    I think Oracle did the great job with introducing the Express to this "fire&forget" market. The installation is a snap, it just works out of the box, nothing serious to configure, opposite to what I remember from installing and working on Oracle 9 a few years ago. In some places it's still "you need to start SQL*Plus and enter this script", but it's definitely less than before. I also find the SQL Developer a great tool, it can do most of what we need to do with the DB, it's also much better and pleasant to use over Oracle 9 tools. Still, a few basic things still require too much hassle, and I'd say taking your schema to another machine is one of them. So I think that, if you do it well, the "schema copy wizard" you mentioned might be very helpful. If I was to give any general advice for Express line of DB/tools, I'd say "make things simple" - make it "a DB you can't see".
    That's, IMHO, the way to attract more Express users.

Maybe you are looking for

  • Iphoto event date wrong

    How do i correct the date which is automatically assigned to my iphoto events?  Every event in iphoto says January even though when looking at the description info for each photo, the "date taken" field is accurate.  Iphoto seems to be keeping the da

  • SVN subclipse Plugin should be integrated by default in FLEX 3

    Hi, SVN is now the standard Versioning system. SVN subclipse Plugin should be integrated by default in FLEX 3 http://subclipse.tigris.org/install.html

  • How do you add into a group a contact you added onto your i-phone?

    How do I put into a group a contact I added to my i-phone 6?

  • Ajax tags in jspx page

    hi i want to use ajax tags in my jspx page, for that i am using the fallowing *<%@ taglib uri="http://java.sun.com/blueprints/ajaxtextfield" prefix="aj" %>* but i got an error when i compile the page as Illegal token can any one help... thanks in adv

  • Query Error - Help Please

    The query below returns this error message: "ORA-00918: column ambiguously defined" It points to the last line of the query, at 'Colour' before the equals.... WITH  ranked_data  As      SELECT Members_Order.Catalogue_ID, Item.Item_Description, Item.C