Multiple decimal separators

Hi Team,
I have a requirement like I will get a data file from external system. I have some columns to validate like
All percentage and amount fields are checked on multiple decimal separators and non numeric characters.
Can anyone can give me guidance to achieve it.
Cheers
Sriram.

From my point of you need to validate that , flat file data is in proper number format or not ?
for that i have listed one funtion that will help you
CREATE OR REPLACE FUNCTION isNumber(arg IN VARCHAR2) RETURN NUMBER IS
n NUMBER;
BEGIN
     BEGIN
          n := TO_NUMBER(arg);
          EXCEPTION
               WHEN VALUE_ERROR THEN
                    RETURN 1;
               WHEN INVALID_NUMBER THEN
               RETURN 1;
     END;
     RETURN 0;
END isNumber;
Now Try like this
Select * from table where isnumber(columnname) = 1 /* to find the invalid number rows */
Same as you can create the % function also.
Thanks
Pranav

Similar Messages

  • Creating external table - from a file with multiple field separators

    I need to create an external table from a flat file containing multiple field separators (",", ";" and "|").
    Is there any way to specifiy this in the CREATE TABLE (external) statement?
    FIELDS TERMINATED BY "," -- Somehow list more than just comma here?
    We receive the file from a vendor every week. I am trying to set up a process for some non-technical users, and I want to keep this process transparent to them and not require them to load the data into Oracle.
    I'd appreciate your help!

    scott@ORA92> CREATE OR REPLACE DIRECTORY my_dir AS 'c:\oracle'
      2  /
    Directory created.
    scott@ORA92> CREATE TABLE external_table
      2    (COL1 NUMBER,
      3       COL2 VARCHAR2(6),
      4       COL3 VARCHAR2(6),
      5       COL4 VARCHAR2(6),
      6       COL5 VARCHAR2(6))
      7  ORGANIZATION external
      8    (TYPE oracle_loader
      9       DEFAULT DIRECTORY my_dir
    10    ACCESS PARAMETERS
    11    (FIELDS
    12         (COL1 CHAR(255)
    13            TERMINATED BY "|",
    14          COL2 CHAR(255)
    15            TERMINATED BY ",",
    16          COL3 CHAR(255)
    17            TERMINATED BY ";",
    18          COL4 CHAR(255)
    19            TERMINATED BY ",",
    20          COL5 CHAR(255)
    21            TERMINATED BY ","))
    22    location ('flat_file.txt'))
    23  /
    Table created.
    scott@ORA92> select * from external_table
      2  /
          COL1 COL2   COL3   COL4   COL5
             1 Field1 Field2 Field3 Field4
             2 Field1 Field2 Field3 Field4
    scott@ORA92>

  • Decimal separators in Fullclient and Webi

    we are using english and german fullclient reports in Webi and show different decimal separators for each published language. Under 6.5 we controlled decimal separators with the language of the publishing-user. The information was stored in the report and was correctly displayed for each user in Webi. This behavior changed unter XI 3.1, the language information for Webi is fixed to the admin account. Under XI we have the problem, that all reports are display either in english or german format, independently from the language of the publishing account.
    The only way to solve the problem is to use the translation manager. But this only work with webi-reports and we can´t convert to this format, because the fullclient reports are to complex. A second way is to change the cell format to sting and replace comma with point. But this doesn´t work, because the excelexport is not able to calculate in this cells.
    Does any body know a solution?

    Hi Eddy,
    This does sound like a bug. As a workaround, are you able to use a whole number and divide it by 10 to give you the same effect e.g. 18,30* (7/10)?
    Regards,
    Michael Amadi
    Please use the 'Mark as answer' link to mark a post that answers your question. If you find a reply helpful, please remember to vote it as helpful :)
    Website: http://www.nimblelearn.com, Twitter:
    @nimblelearn

  • Restricting input to integers, display with comma separators

    I'm using Acrobat 8 on a Macintosh. My question is very similar to the previous one about truncation. I have a small array that adds and subtracts fields, and sums them to totals. The following scripts restrict the data entry exclusively to numbers, but my problem is that it doesn't display my fields in Acrobat with comma separators, e.g., 123,456. Is there a better way of doing this, or is it just a matter of adjusting the formatting script?
    Using a custom script under Format:
    Custom Format script:
    event.value = "(" + eventvalue +")";
    Custom Keystroke Script:
    event.rc = /^[0-9]*$/.test
    (event.change);
    Bill Lomax

    I'm not aware of any cultures that allow multiple consecutive separators, and of course "en-US" certainly doesn't. I think you answer is just that TryParse isn't as smart as you would like it to be.
    If you know how many digits there are after the decimal point, you could use ToString to convert the decimal back to a string and verify that it is the same as the original string. For example, if the string has a currency symbol, thousands separators and
    two decimal places, you could use the following:
    Dim result As Decimal
    Decimal.TryParse(Me.tbxkWhCost.Text, System.Globalization.NumberStyles.AllowThousands _
    Or Globalization.NumberStyles.AllowDecimalPoint Or Globalization.NumberStyles.AllowCurrencySymbol, Nothing, result)
    If result.ToString("C2") = Me.tbxkWhCost.Text Then
    'String is good
    Else
    'String is bad
    End If
    I realise that this doesn't work if you don't know what format the number will be in.

  • How to Format a number to support multiple languages

    I am trying to format a number so that it shows up with the corret decimal separators and thousands separators for different regions/languages, but can't seem to.
    123456.223 is 123,456.223 (US English) and 123 456,223 in French (France)
    I don't know how many such regional settings are being used and what the decimal and thousands separators are.
    If you set the Format to 'System Default Number Format', all is well (But I have to live with 2 digits after the decimal). However, if I want to customize it by saying choosing one of the preset formats or using 'Customize'(say 3 digits after the decimal, for example), then, if I am designing the report in US English setting, the separators from that setting are used, even when the report is generated in French locale. Even if I try to put in a condition for these separators and use 'DefaultAttribute', it doesn't seem to help.
    One workaround is to format the number as a string and display the string instead (this time use ToText() function and provide the no. of decimal places needed). But I have aggregations based on this field and they don't work in with string fields.
    Could someone advise me if there is a way to solve this problem? (I'm hoping that there is some way, perhaps an easy one to overcome this problem.) It seems anytime I want to change the default setting, the current values are stored and used irrespective of the reigonal setting.
    Any help is greatly appreciated.
    Thank you,
    Raghu

    Use the default settings and then it should format according to the local PC settings.

  • Problem with thousands and decimal  separator (Excel 2000)

    Hi, i have a problem with the download option to excel 2000.
    When downloading numbers over 1000 the thousands separators change in decimal separators.
    My config is:
    Locale (location): Español - España
    User Interface Language: Español
    For example, if I have a value as 1800:
    1) in OBIEE show "1.800" (ok)
    2) in Excel 2000 show "1,8" (bad)
    If i choose Locale (location): English - United Stated and
    User interface language Español.
    1) in OBIEE show "1,800" (bad)
    2) in Excel 2000 show "1.800" (ok)
    Can someone help me solve my problem?
    I need to show the same result in OBIEE and Excel, that is, "1.800" with "." not with ",".
    Thanks

    Hi,
    The thousands separator change in the backend dind't work. (+ it only works for text input fields, not for text fields)
    Anyhow, this is how we created a workaround :
    Suppose we did this : <b>NSTR(@CREDITLIMIT,"C.2")</b>
    This resulted in the field being displayed as <i>67,234.56</i>
    The 'dirty' way to convert this to an european format is :
    <b>REPLACE(REPLACE(REPLACE(NSTR(@CREDITLIMIT,"C.2"),",",";"),".",","),";",".")</b>
    Output is <i>67.234,56</i>
    (we just replaced the '.' by ',' and vice versa)
    I still feel quite uncomfortable with this solution, but this is the only way we got it to work.
    I really hope a next patch/servivepack provided a more elegant solution for this problem... (hint hint)

  • Decimal places diferent in BO SUM function than from DB

    Hi,
    I have a column from a Netezza database with 2 decimal places, if I apply a sum() function in BO (report) the decimal places are 4.
    The strange part is that if i do exact the same query in a DB2 database the decimal places are always two (like in DB) even if i use a sum function in report.
    There is some configuration regarding the database i'm using to set the decimal places in the report level to be the same than in DB?
    Edited: I've been studing the problem and I found using a odbc instead of a jdbc makes all the columns have 2 decimal places, and the sum problem doesn't happen. Now my issue is the division. How is possible that with the exact same values with two decimal positions, in BO and exporting to excel the last decimal place is different in some cases
    Example:
    Lets say A/B with A=13549678065,560000 and B= 21629484348,690000. With Netezza result is 62,6444803173527 and Db2  62,6444803173528
    Thanks for your time.

    I've never seen this particular problem before. Quite strange. It sounds more like an OLAP or SQL Server issue, not BPC.
    I'm not aware of any configuration on SQL server that allows you to control the decimal separator.
    I had a similar problem in the past, when my customer refused to follow the install guide instructions, and insisted that the server be set to non-US English regional settings. If I recall, the issue had to do with date formats not decimal separators. They ended up un-installing and re-installing the entire OS (with US English setup, the second time around), and then it worked fine. This was back on 5.0, and perhaps the situation has changed since then. There's a section in the master / install guide that covers the server-side language & regional settings in some detail.
    But before you look at that, try something easier -- is it possible that the cube is somehow corrupted? Do you get any errors when you process the application? Perhaps there is some data in the fact table with an invalid member ID.
    Do you get the same result in your Excel report when you use both EVDRE and EVGET?
    And if you browse the cube data in SQL Mgmt Studio (logging into the Analysis Services cube) do you see aggregated data there?
    Regards,
    Tim

  • Decimal Problem in fields

    Hi,
    In Export invoice we are entering currency in USD.When we enter the value it accepts 3 decimal places.But it is stored as 2 decimal places in table.
    Eg.2.059 USD in invoice screen
    but in table 20.59 USD.
    What is the problem?where we can rectify this error?

    It will be stored with two decimal places. No issues with that. when you display this on your report, you have to specify the currency as USD and your issue will be resolved.
    write: v_amount to v_amount currency 'USD'.
    I am quoting from the help of the write statement below.
    This addition defines currency-dependent decimal places for the output of data objects of data types i or p. For all other data types, except for f, the addition is ignored. For cur, a three-digit, character-type field is expected that contains a currency key from the column CURRKEY of the database table TCURX in uppercase letters. The system determines the number of decimal places from the column CURRDEC of the respective row in the database table TCURX. If the content of cur is not found in TCURX, two decimal places are used. The following applies for numeric data types:
    In the case of data types of type i, a decimal separator is inserted at the position determined by cur and the thousands separators are moved accordingly.
    In the case of data objects of type p, the decimal places defined in the definition of the data type are ignored completely. Irrespective of the actual value and without rounding actions, the decimal separators and the thousand separators are inserted at the positions in the numbers determined by cur.
    In the case of data objects of type f, the addition CURRENCY has the same effect as the addition DECIMALS (see below). Here, the number of decimal places is determined by cur.
    If the addition CURRENCY with length specification * or ** is used after AT, it is used first and the output length is determined from the result.
    Note
    The addition CURRENCY is appropriate for the display of data objects of type i or p without decimal places, whose contents are currency amounts in the smallest unit of the currency.
    Example
    The output of the WRITE statement is "123456,78".
    DATA int TYPE i VALUE 12345678.
    WRITE int NO-GROUPING CURRENCY 'EUR'.

  • How do I change the decimal separator from a comma to a dot in numbers? I upload my bank statements into numbers and all contain dots. Numbers does not understand the dots.

    Hi,
    I am a recent convert from Exell to Numbers.
    I have downloaded my bank statements to Numbers. The bank statement uses dots as decimal separators, whilst the Numbers default is a comma.
    I need to change the Numbers format to dot to avoid having to manually change all in the downloaded spreadsheet.
    This spreadsheet also includes my currency as R (ZAR Rands), so either need to remove these or get Numbers to understand it, again to avoid having to remove/change all manually.
    Would really appreciate your help.

    Hi,
    Thanks for your response. Have figured it out with the help of Ross at the V & A Waterfront Apple Store.
    System Preferences- Language and Region- at the bottom of the box click "Advanced"- then choose the dot/ comma under Number separators- Decimal and again under drop down box "decimal" under currency.
    Regards
    Teana

  • Round to two decimal places

    my cost per month textbox typically returns multiple decimal places, is it possible to limit it's output to two decimal places like real monetary calculations?
    calculatebutton.addEventListener(MouseEvent.CLICK, doMyCalculation);
    calculatebutton2.addEventListener(MouseEvent.CLICK, doMyCalculation2);
    costpermonth.restrict = ".0-9";
        var myAnswer : Number;
        myAnswer = Number(costofitem.text) - Number(amountsaved.text);
        amountneedtosave.text = String(myAnswer);
    function doMyCalculation2(e:MouseEvent):void
        var myAnswer2 : Number;
        myAnswer2 = Number(amountneedtosave.text) / Number(howmanymonths.text);
        costpermonth.text = String(myAnswer2);

    use the toFixed() method of numbers:
    amountneedtosave.text = myAnswer.toFixed(2);

  • Change of decimal separator

    Is it possible to change the decimal separator for importing data?
    I have data with , as separator can I change the default Point to comma?
    Thanks for your interest
    Thomas Pfeiffer
    Message Edited by Thomasrp on 02-16-2006 10:10 AM
    Solved!
    Go to Solution.

    I really don't understand your problem, because normally DIAdem can import both types of decimal separators... If you use the ASCII Import the important is that you use the proper configuration for your file type… and if this file uses the comma as a decimal separator, the delimiter character between data will not be a comma… DIAdem should import the data with no problem, but on DIAdem you will see always the "." (dot)
    If your problem is that on the DIAdem View you want to see the "," comma you can do the following:
    - Right mouse click, and select "Table Settings"
    - Change the numeric format, for example "dd,ddd" then you will see only 3 decimal places and the decimal separator will be the comma.
    Hope this helps you,
    Marc.

  • GeoRaptor 3.2.1 Released for SQL Developer 3.x

    Spatialites!
    After 6 months of development and testing, GeoRaptor 3.2.1 has been released for SQL Developer 3.x (tested on 3.0, 3.1 and 3.2). This release no longer supports SQL Developer 1.x or 2.x releases due to internal changes to the SQL Developer APIs.
    GeoRaptor can be downloaded from the GeoRaptor project's sourceforge page: http://sourceforge.net/projects/georaptor and installed via Help>Check for Updates>Install from Local File. Installation via SQL Developer's update mechanism should be available soon.
    The release notes for this release are:
    * Fixed issues with validate geometry functionality in particular the update dialog box.
    * Revamped "About GeoRaptor" form. Includes clickable URLs, links to mailing lists, version number listing, thanks to testers etc.
    * Placed "About GeoRaptor" icon on GeoRaptor's map toolbar.
    * SQL Developer NLS settings accessed: improvements in the display and entry and numeric data.
      -- Tolerances in Spatial Layer properties will display with the NLS decimal separator eg 0,05.
         Some parts of GeoRaptor such as Validation that show and accept numbers have not been changed from when someone else modified the code.
         If you double click on the left MBR/right MBR icon in the map at the bottom, the current centre position will display according to the NLS settings.
         Editing the value to jump the map to that point works even with grouping separators and decimal separators being commas!
    * Spatial Layer Draw has been modified to use NLS based decimal formatting.
    * New geometry marking/labelling options have been added. In particular you can now label the vertices of a linestring/polygon with the following additional elements:
      -- Cumulative length
      -- Measure (M)
      -- Z value
      -- Labelling of vertices with <id>{X,Y} now also honours 3/4D geometries. If geometry has XYY then it will be labelled as {X,Y,Z} etc.
    * You can also label each vector/segment of a linestring/polygon with:
      -- Length
      -- Cumulative Length
      -- Bearing (approximate for geodetic/geographic data)
      -- Distance (approximate for geodetic/geographic data)
      -- Bearing and Distance (approximate for geodetic/geographic data)
    * The font properties of the mark text can be changed independently of the feature label. This includes the offset and label position (CC, LL, UR etc).
    * New feature labelling options have been provided:
      -- First/middle/last vertex,
      -- Any supplied sdo_point within a line/polygon's sdo_geometry object, or
      -- Calculated by GeoRaptor on the client side using Java Topology Suite.
    * Result sets now have the ability to:
      -- Copy to clipboard all geometries across many rows and columns.
      -- Display one or more (selected) geometries in a popup image window. This functionality is also available in the result set generated by an Identify command.
    * New GeoRaptor Preferences:
      -- Width and height in pixels of the new popup image window (displaying one or more geometry objects) can be set;
      -- Colours of orphan, missing and correct metadata entries for Metadata Manager;
      -- Prefixing with MDSYS for all currently supported spatial objects - sdo_geometry, sdo_point, sdo_elem_info, sdo_ordinates, sdo_dim_info - has been made an option.
      -- There is now a new property called "Show Number Grouping Separator" in Tools>GeoRaptor>Visualisation.
         If it is ticked a number will be formatted with the thousands separator in Tools>Database>NLS eg 10000.000 will display as 10,000.000.
    * Sdo_Geometry display of all spaces in text between elements of the sdo_geometry array have been removed.
       This was done mainly to compact the sdo_geometry strings so that they are as small as possible when displaying or copying to clipboard.
    * Help pages added to the following dialogs with more to follow:
      -- Metadata Manager,
      -- Shapefile Importer and
      -- Layer Properties dialogs.
    * GeoRaptor menu entries renamed. New "Manage All Metadata" entry added to View>GeoRaptor menu.
    * Spatial Index creation dialog now supports additional index parameters and parallel build settings.
    * Metadata Manager overhauled:
      a. Shows:
         1. Metadata entries which have no underlying oracle object (orphan)
         2. Metadata entries for existing underlying objects (existing case)
         3. Database objects with sdo_geometry for which no metadata entry exists (new)
      b. All orphan/existing/missing colours for (a) can be set via Preferences>GeoRaptor>Visualisation
      c. All actions for main (bottom) metadata table are in a single right mouse click menu.
         Some entries will only appear if a single row is selection (metadata copy), others (delete and copy to clipboard) will appear for one or more.
      d. Can now switch between open connections to modify metadata of other objects in schemas other than the starting object.
      e. Buttons revamped.
    * Tab/Shapefile export:
      a. Export now supports NULL valued columns. Can be exported as an empty string (if DBase override in GeoRaptor Preferences is ticked) or
         as a predefined value eg NULL date => 1900-01-01 (set in new GeoRatptor Import/Export Preferences).
      b. Some work attempted on export of NLS strings (still not corrected).
      c. Objects with no rows now correctly processed.
    * Shapefile Import
      -- Bug relating to Linux file names corrected.
    * Fixed issue (identified by John O'Toole) with spatial index underlying a view not being used in map display.
    * Reinstated sdo_nn as the principal method for Identify (requested by John O'Toole).
    * Fixed problem with handling single click zoom in and out in GeoRaptor map etc.
    * Fixed problem with rendering lines from database item (identified by Vladimir Pek).The new "About GeoRaptor" should be read by all people installing GeoRaptor.
    Please, please consider registering your email address with our private email list so that we can get a feel for the sorts of people downloading and installing GeoRaptor.
    Please consider helping us with documentation or the internationalisation via translating properties files from English to your native language.
    GeoRaptor is written and maintained by people who use SQL Developer and Spatial every day but we don't pretend we know everything that users want: please let us know via our feature request page at SourceForge.
    We don't get paid for what we do so are always looking for additional help.
    Here are some of the requests we have had for improvements:
    1. MySQL access
    2. WMS access;
    3. Ability to import shapefile data into an existing table;
    4. Ability to processing multiple shapefiles into separate tables (current version can import one or more into a single target table);
    5. Ability to export/import layer definitions to give to others;
    6. Support for non-English character sets for varchar exports to shapefiles.Some are relatively simply, some require a lot of engineering work. For the latter, we are considering alternative funding methods to the currently completely free development approach.
    Thanks to the following for their invaluable assistance:
    Holger Labe, Germany
    John O'Toole, Ireland
    Vladimir Pek, Czech Republic
    Pieter Minnaar, Holland
    Olaf Iseeger, Germany
    Sandro Costa, Brazil;
    Marco Giana, Australia.regards
    Simon Greener
    Principal GeoRaptor Developer
    Edited by: Simon Greener on Sep 10, 2012 2:43 PM

    Simon,
    I will admit, I almost never use SQL Developer. I have been a long time Toad user, but for this tool, I fumbled around a bit and got everything up and running quickly.
    That said, I tried the new GeoRaptor tool using this tutorial (which is I think is close enough to get the jist). http://sourceforge.net/apps/mediawiki/georaptor/index.php?title=A_Gentle_Introduction:_Create_Table,_Metadata_Registration,_Indexing_and_Mapping
    As I stumble around it, I'll try and leave some feedback, and probably ask some rather stupid questions.
    Thanks for the effort,
    Bryan

  • Logic Pro X v10.0.7 is out

    http://support.apple.com/kb/TS4498
    this is a looooong list

    ...and the full list of changes and fixes .......
    Logic Pro X 10.0.7 update
    New Features and Enhancements
    It is now possible to insert the current values of volume, pan, and all active sends of selected tracks as automation points at the playhead position. The new functions are accessible as a menu option or key command.
    It is now possible to paste track automation data at the Playhead or Marquee selection location.
    A new MIDI Project Setting allows MIDI CC 7 (volume) and MIDI CC 10 (pan) messages to control the instrument plug-in instead of the channel strip.
    The output of Auxiliary channel strips assigned to Tracks will now generate audio files when using any of the following Export menu options: "Region as Audio File," "Track as Audio File," or "All Tracks as Audio Files."
    Logic now supports up to 24 processing threads on computers with 12 cores.
    All menu items related to Snap, Alignment Guides, and "Snap to Grid" settings have been consolidated into the Snap menu in the Main window.
    It is now possible to activate/deactivate multiple plug-ins on a channel strip by vertically click-dragging the mouse over their power buttons.
    An auto-saved version of a project now contains the Undo History of the project from which it was derived.
    It is now possible to install the Logic content to an alternate system drive even if the Logic application is not installed there.
    Activating Auto Punch with a key command or Marquee selection now automatically adds the Autopunch button to the Control Bar.
    It is now possible to use modifiers with the Velocity Slider in the Piano Roll and Score Inspectors to change its behavior in the same way as the Velocity tool. Holding Option allows velocities for notes to continue to be changed even when other notes have reached there minimum or maximum MIDI velocity value. Option-Shift sets all notes to the same velocity value.
    The Scissors tool now works on arrangement markers.
    It is now possible to drag a Summing Stack into a Folder Stack.
    It is now possible to use the Beat Map feature with a track that has Flex enabled.
    Flex Transient Analysis can now be aborted by pressing Command-period.
    When a Transient Marker is inserted near the position of a previously deleted transient in the Audio File window, the marker will now only snap to the position of the deleted marker if the Option key is pressed while inserting it.
    It is now possible to create more than 32 Folder Track Stacks in a project.
    It is now possible to adjust sliders in the Mixer when controlling Logic via screen sharing, Apple Remote Desktop, or other VNC clients.
    It is now possible to access the Recent Projects menu while the Open Project dialog is active.
    It is now possible to remove the Master Output track from the Tracks area.
    The master track of a Track Stack can now be designated as Groove Master.
    Audio waveforms are now visible under automation on the master track of a Track Stack.
    The Track Import window now shows plug-in preset names.
    When Logic imports Final Cut Pro X XML, it now organizes audio tracks according to their assigned roles in Final Cut Pro.
    Audio is now exported as 24-bit in projects exported to Final Cut Pro X XML.
    When importing XML files that contain multiple projects from Final Cut Pro X 10.1 or later, Logic Pro X now offers a dialog to pick a specific project to import.
    The 1/2 Note head symbol is now available in the the Score Part Box.
    The Catch Playhead button is now available in the Score when the Advanced Tools preference is disabled.
    It is now possible to load ".caf" format files into Space Designer with the Load IR file selector.
    There is now a new key command to trim the start of a region to the end of the previous region in the track.
    There is now a dedicated Piano Roll section in the Key Commands window. This includes commands for "View Mode: One Track," "View Mode: Selected Regions," and Toggle View Mode.
    There is now a key command for “Detect Tempo of Selected Region.”
    There is now a key command for “Adjust Tempo using Beat Mapping Track.”
    The timeline in Logic Remote now changes color to indicate Logic is in Sync mode.
    It is now possible to use the Option key to insert a mono plug-in between two existing plug-ins on a stereo channel strip or vice-versa.
    The Velocity Processor MIDI plug-in now displays note-on as orange dots and note-off events as blue dots in the compression curve window.
    Command-click on a vector point can now be used to modify the times of all subsequent points in the ES2 Vector Envelope.
    The Distortion II plug-in now offers a Distortion Output Level and Mix control.
    Stability
    Logic no longer sometimes quits unexpectedly when:
    Using the Option key to toggle all the disclosure triangles in the Project Audio window.
    Dragging audio from the Project Audio window to the Tracks area.
    Defining custom bank messages for a Multi Instrument in the Environment.
    You insert a blank recordable DVD while Logic is running.
    Changing the audio buffer size while the Audio Editor is open in Flex Pitch mode.
    Selecting a font in the Number & Names panel of the Score preferences.
    Deleting a group in the Project Audio window.
    Undoing a flex edit.
    Using the Glue tool on flex pitched notes after having switched from the Audio File Editor to the Audio Track Editor.
    Performing undo and then redo in quick succession on an EQ in the Smart Controls.
    Performing Undo after deleting a comp or take.
    Closing a song while importing a MIDI file.
    Enabling phase-locked editing on a group.
    Using the Pencil tool in the Audio File editor.
    Importing a long MP4 (AAC) file.
    Changing a channel strip input from stereo to mono.
    Disabling Core Audio.
    Playing a Drummer track while downloading and installing new content.
    Performing undo after certain operations.
    Pasting channel strip settings in the Mixer.
    Dragging a MIDI region over the Score editor.
    Hot-plugging an Apogee Duet to a computer running OS X Mavericks.
    Importing a patch that includes a Track Stack.
    Adding AAC files containing Audio Transport Stream Data (file type “.adts”).
    Performance
    The Channel EQ no longer causes unexpected CPU spikes in live track mode on MacBook Pro with Retina Display.
    Logic no longer becomes less responsive after making several adjustments to the size and/or position of a floating Transport window.
    There is no longer a delay opening the list when clicking in a Send or Output slot on a channel strip.
    Logic no longer becomes less responsive when working for long periods with Flex Pitch.
    The Drummer track now reliably maintains proper timing if it is selected with Low Latency mode enabled.
    Control points in the Transposition track now move more fluidly when edited.
    Scrolling a channel strip fader in the Inspector with a mouse wheel now adjusts its value at the correct resolution.
    Comping takes is now more responsive when Flex Time is enabled.
    Playing a Touch Instrument in Logic Remote no longer sometimes leads to hung notes in Logic Pro X.
    Improves responsiveness when dragging tempo events in the Global tempo track.
    Songs with a very large number of regions now play back as expected.
    Logic’s performance has improved when previewing notes in the Score, Piano Roll, and Event List for regions on a track other than the one selected.
    Multi output Software Instruments with complex routings no longer sometimes cause Logic to become briefly unresponsive when starting playback.
    Logic now reliably creates thumbnails to the end of the video track with long movie files.
    Selecting Channel Strips in very large projects is now faster.
    Improves compatibility with ProRes movie files on OS X Mountain Lion v10.8.5.
    When scrolling over an open Take folder at high zoom levels on OS X Mountain Lion v10.8.5, there are no longer unexpected spikes in CPU usage.
    Automation
    Clicking on an event in the Score no longer sometimes selects the wrong events.
    It is now possible to paste automation at the playhead or marquee selection area rather than only at its original position.
    All MIDI Draw data created by moving track based automation to a Region now appears on the Region and in Piano Roll as expected.
    Volume automation moved from a track to a region is now displayed in the Tracks area MIDI Draw view as expected.
    It is now possible to use MIDI Draw for an event type that does not yet exist in the region.
    When track based automation is moved to a region, the region now immediately switches on MIDI Draw to show the automation in the Track area.
    When region automation is moved to a track, the automation now starts at the beginning of the track.
    MIDI Draw now reliably creates Surround Diversity and Surround Angle fader events in regions.
    It is now possible to make a Marquee selection over region loops when automation is visible.
    MIDI Draw data is no longer shown on additional automation lanes when the main automation lane is set to “Off.”
    MIDI Draw no longer incorrectly displays a ramp between isolated Pitch Bend events.
    When switching between MIDI takes, the MIDI Draw area now properly updates to show the currently selected take.
    Option-clicking a MIDI Draw point again selects all following MIDI Draw points for the region.
    MIDI Draw points inserted with the Pencil are now reliably placed at the clicked position.
    Audio no longer glitches when editing automation while playing back.
    Score
    It is now possible to deselect a voice in the Staff Style window by Command-clicking it.
    The floating Part Box window in the Score no longer shows overlapping elements when first opened.
    Clefs in the Staff Style window now scale properly when viewed on a Retina display.
    Rests in Mapped Drum styles are now correctly positioned with their associated drum groups on the staff.
    When printing a score part with Advanced Tools disabled, Logic no longer prints the track name twice.
    Changing the split point of one voice in a multi-stave Staff Style now properly affects the other voices assigned to the same channel.
    Page view of scores in songs created in Logic 9 now retain their proper paper size when opened in Logic Pro X.
    Scores printed as PDF files now render properly when viewed in Adobe Reader.
    The cursor now reliably shows the correct tools when editing the score in linear display mode.
    It is no longer possible to give a new Score Part Box a name that is already in use by another Part Box.
    The font names for Jazz Cord and Swing Cord fonts now display correctly in the Root Font and Chord Extension Font display in the Chords & Grids panel of the Score settings.
    The staff display in the Staff Style editor now shows the proper key signature for transposed styles.
    It is now possible to change settings for multiple selected staves in the Staff Style edit window at the same time.
    Pasting a compound time signature in the Signature track no longer corrupts the time signature display in the Score.
    Filter buttons on floating part boxes in the Score now remain visible when the part box is resized.
    Tap to click on a trackpad now works with the Pencil tool in the Score.
    It is again possible to insert a bar line at the end of a region in the Score.
    The pencil tool again works in the Score when assigned to the right mouse button.
    In the Score, selected notes in loops now show the selection color.
    The Part box is no longer empty when first opened in a stand-alone Score window after recording.
    The print border no longer sometimes changes unexpectedly when printing to PDF from the Score.
    When Select All is used within a Score Set, the selection is now properly limited to regions within the Score Set.
    Tooltips no longer sometimes obscure the guidelines when inserting elements into the Score.
    The bar positions of SMPTE locked notes now update properly in the Score after the tempo is changed.
    Pressing the Control key now allows for finer granularity when editing Duration Bars in the Score.
    Undo now works after pasting Staff Styles.
    Undo now works after changing the Low or High note value in a Staff Style.
    In page view, the Score now correctly updates to reflect a different paper size selected in the Page Setup window.
    Track names are now reliably shown in Page View when the track contains overlapping regions.
    Drag handles now remain visible at all zoom settings when dragging parts into the Score in linear view mode.
    Adding special bar lines next to added clef or signature changes in linear view mode no longer causes the bar lines and clef or signatures to overlap.
    The mouse cursor now reliably shows the currently active tool in the Score.
    The Score now displays as expected after scrolling vertically at high zoom settings.
    Copy/paste of notes across multiple staves in the Score now works properly.
    Custom colors defined in the Score Layout window are now recalled properly when Logic is relaunched.
    The text cursor is now easier to see in various fields in the Score window.
    The Display Level button in the Score now follows the entire Score hierarchy when an Instrument Set is in use.
    The cursor now displays the Length Change tool when held over the end of a Duration Bar in the Score.
    It is again possible to assign no clef or a drum clef to non-mapped score styles.
    Plug-Ins
    Importing plug-ins to a track no longer unexpectedly changes the input source on the track.
    The pitch of notes held when using Sculpture or ES2 are no longer sometimes shifted when using non-Equal Tempered tunings.
    Moving the Delay slider in the Note Repeater MIDI plug-in while notes are repeating no longer results in hung notes.
    The cycle length in the Arpeggiator plug-in now reliably updates when set to Grid mode.
    Recall Default now works with the Delay Designer plug-in.
    Recall Default now works properly with Audio Unit plug-ins.
    It is now possible to activate bypass on plug-ins that are not currently available.
    When the I/O configuration of a plug-in is changed, its editor no longer opens.
    The timing of multi-output software instruments is now maintained when latency inducing plug-ins like the Ad-Limiter are used on the main output.
    Audio files created by the "Export All Tracks as Audio Files" command now maintain proper sync in projects where high latency plug-ins are used in Summing Stacks.
    The Expander plug-in no longer sometimes introduces audio crackles with certain source signals.
    With Beat Sync disabled, the Course Rate control in the Auto Filter plug-in again behaves as expected.
    Audio now plays reliably from tracks in which there are two Tube Burner pedals inserted in the Pedalboard plug-in.
    VoiceOver now works reliably to activate Smart Controls for the Vintage Clav and Vintage B3 Organ plug-ins.
    Improves the behavior of Smart Controls when used with Voiceover.
    The stand-alone Smart Controls window now properly remembers its last state when reopened.
    When editing vector points in ES2 in loop mode, all envelope values are now properly shown as percentages when the envelope is time-synced.
    Shift-clicking can again be used to insert a vector point in the ES2 Vector Envelope.
    In the ES2 Vector Envelope, the Delete Selected Point contextual menu item again works as expected.
    EXS instruments created in EXS24 MK I no longer exhibit unexpected random velocities when played.
    Logic no longer changes a user-assigned track color when swapping Software Instruments.
    Space Designer’s Filter and Density controls now remain active when the plug-in window is opened more than one time in a session.
    Projects with multiple Ultrabeat instances now play back with reliable timing when the Process Buffer Range is set to Small in the Audio > Devices preferences.
    A plug-in inserted on the 16th slot of an audio channel strip or the 15th slot of a Software Instrument channel strip now remains visible.
    The percussion controls in the Vintage B3 now respond as expected to knob movements from the Native Instruments B4d remote control.
    The mapping of value to position for the Organ sliders in the Smart Controls window is now consistent with the sliders in the Vintage B3 Organ.
    In the Mixer, it is now possible to drag a plug-in from one channel strip to another when there is an External MIDI channel strip between the source and target.
    One shot samples triggered in EXS24 no longer play back with clicks when Rewire Live Mode for Rewire is disabled.
    All plug-in windows now reliably open after changing the order of plug-ins in a channel strip.
    The Scripter plug-in now reliably triggers notes when playing back outside of an active cycle zone.
    The meters in stereo instances of the Adaptive Limiter plug-in now show independent levels for the left and right channels.
    Tuned taps in the Delay Designer plug-in now reliably play in sync.
    Flex
    Flexed regions no longer sometimes show waveforms in the wrong positions.
    Flex Markers no longer unexpectedly change positions when moving them in songs that contain tempo curves.
    Logic no longer sometimes incorrectly shows that an audio region is flexed in songs that contain tempo changes.
    If Flex is enabled, Logic now properly includes manually added transients when an audio region is converted to a sampler track.
    Flex Pitch controls are now available in the Tracks area and Audio Editor immediately after Flex Pitch is enabled for a track and analysis is complete.
    Setting a Flex Mode now applies to all selected tracks.
    It is again possible to cancel flex analysis before it completes.
    The Transposition Track now works with flex-pitched regions.
    Flex mode now gets enabled for all tracks in a group even if Group Clutch enabled.
    The Audio Track editor now reliably shows all notes when scrolling with Flex Pitch enabled.
    Logic no longer sometimes hangs when adjusting notes in Flex Pitch.
    The Flex Pitch grid is now displayed for all takes in the Track Editor even when a Software Instrument track is directly above the selected Audio track.
    Logic now offers the option “Do not show again” in the alert dialog that reads "This region contains inactive flex markers, which will be deleted if you perform the edit."
    If a Flex mode has already been set, clicking the Flex drop-down menu will correctly highlight the currently selected Flex mode.
    When dragging a region from one track to another, the region "Flex and Follow Tempo & Pitch" checkbox settings are now maintained as expected.
    Transient detection is improved with quieter source material.
    When Flex is bypassed on a Take folder, the Follow Tempo checkbox is also now disabled.
    General
    Resolves several issues with Snap introduced in Logic Pro X v10.0.6.
    "Snap to Relative Value" now reliably works at all zoom levels with Smart Snap enabled.
    Adjustments to the left border of a region now use relative snap when that option is enabled.
    When Alignment guides is enabled, Snap to Absolute value now works with Cycle.
    Alignment Guides now work as expected when Snap is set to Off.
    The track icon picker now activates with the first right-click or Control-click.
    Toggling the Tracks Inspector no longer sometimes activates Alignment Guides.
    Logic no longer incorrectly shows an alert that the content must be installed the first time it is launched on computers purchased with Logic pre-installed.
    The Capture as Recording key command no longer creates odd length regions when used in songs with time signatures other than 4/4.
    The Hide Step Input Keyboard key command again works as expected.
    The Nudge Region to Nearest Beat option in the Adjust Tempo using Beat Detection dialog now works as expected.
    The Snip at Playhead Position key command no longer sometimes causes notes in the new righthand region to shift to the beginning of the region.
    Logic Pro X no longer displays the error “Could not open source file” when opening certain MP3 files.
    Logic now properly includes time signature, key signature, and tempo events when moving Arrangement markers.
    Undoing the repositioning of an Arrangement Marker now correctly moves affected automation back to its original position.
    Command-dragging one arrangement marker over another now replaces the previous marker as expected.
    Colors assigned to arrangement markers now take effect as soon as the color is clicked in the Color Box.
    It is now possible to use the Marquee stripe to delete a section within the area encompassed by an Arrangement Marker.
    Using the "Split at Playhead" command on the last arrangement Marker in a song now properly sizes the arrangement marker to the right of the Playhead.
    When an arrangement marker is split, the new marker to the right now maintains the same color and name as the original.
    Arrangement markers can no longer be inadvertently moved by mouse clicks in an empty area of the Arrangement track.
    Copying Arrangement markers no longer creates extra tempo events.
    The Beat Mapping track now continues to display properly when it is resized after other Global tracks have been resized.
    The Beat Mapping Track no longer disappears if Global Tracks are shown while it is already visible.
    Deleting a connection in the Beat Mapping track now correctly also deletes its associated tempo event.
    Tempo events created in the Global Tempo track now reliably display in the Tempo list.
    Setting one track of a phase-locked edit group as Groove Master or Groove Follower now reliably shows all members of the group as being enabled.
    Time signature changes are now reliably displayed in the timeline.
    Logic no longer re-downloads basic content that has already been downloaded by MainStage.
    Arrange Folders now reliably display as expected in the Mixer.
    Double-clicking on the icon for a folder channel strip in the Mixer now opens the folder.
    Commas may now be used as decimal separators when typing values into controls on the Mixer.
    It is now possible to drag regions vertically without an unexpected horizontal shift when "Snap to Grid" is enabled in the Tracks area.
    Recording a new take over multiple existing regions again works as expected.
    It is now possible to create an empty MIDI region on a track hosting an Auxiliary channel strip.
    Shift-click to delete a take selection again works reliably.
    Region Gain now works as expected when applied to comp segments in a Take folder.
    When a take selection is disabled and then re-enabled, the change is now properly reflected in all tracks that are part of the same group.
    Logic no longer unexpectedly re-extends a shortened Take folder when the folder is dragged vertically to a different track.
    When recording in Cycle mode, Logic no longer creates an automatic comp when a take encompasses only part of the Cycle range.
    When regions are packed into a Take folder, regions from the same track are now placed on the same sub-track in the Take folder.
    Fixes an issue in which it was sometimes no longer possible to change the length of a Take folder after performing several other Take folder length edits.
    Take regions no longer unexpectedly shift horizontally when dragged vertically from one sub-track to another when the "Limit Dragging to One Direction In: Tracks" preference is enabled.
    Copied Take folders are no longer missing their contents in certain rare situations.
    Regions on audio tracks inside a folder now are reliably placed on their proper tracks when the folder is unpacked.
    The key command “Select Previous Section for Realtime Comping” now works correctly when used while recording multiple takes in Cycle mode.
    When Bounce-in Place is used with a channel strip that contains a plug-in that performs a mono to stereo conversion, Logic now creates a mono file if the option to bypass plug-ins is selected.
    Regions created with "Bounce in Place" are no longer sometimes given random names.
    Addresses and rare issue that could cause some MIDI notes to play back at the wrong pitch.
    In Link mode, the Piano Roll now reliably shows the contents of the selected region.
    The Event Float window no longer loses focus after a selected note has been edited in the Piano Roll.
    The "Split Events by Playhead" command now works reliably with multiple notes in the Piano Roll.
    Editing notes in the Piano Roll with multiple regions selected no longer sometimes results in notes being inadvertently moved from one region to another.
    Closing the local inspector in the Piano Roll editor no longer leaves a blank area on the right side of the editor.
    Opening MIDI Draw in the Piano Roll no longer offsets the keyboard into the editing area.
    When adding notes in the Piano Roll with the Pencil, newly created notes again have the same Velocity as the last edited note.
    It is now possible to lasso notes in the Piano Roll editor using a Wacom tablet when Logic’s Right Mouse Button

  • OAF page with XML Publisher report

    Hi All,
    I am trying to create a OAF page with an XML Publisher report. I am not able to create a 'defaultSingleColumn' region which extends '/oracle/apps/xdo/oa/common/webui/DocumentViewerRn.MainRegion', getting a Confirm message and Validation error and they are:
    Confirm message:
    Component "/oracle/apps/xdo/12.0.0/mds/oa/common/webui/DocumentViewerRn.MainRegion" cannot be referenced from
    "/xx/oracle/apps/xxbsk/payslip/webui/PaySlipViewPG.region1" because it violates scope restrictions.
    Are you sure you want to use component "/oracle/apps/xdo/12.0.0/mds/oa/common/webui/DocumentViewerRn.MainRegion"?
    Validation Error:
    The value "oracle/apps/xdo/12.0.0/mds/oa/common/webui/DocumentViewerRn.MainRegion"
    set on the "Extends" property for component
    "/xx/oracle/apps/xxbsk/payslip/webui/PaySlipViewPG" contains multiple naming separators.
    I am trying to develop this page for R12.1.3 and using correct version of JDev (Patch 9879989).
    I am following the below link for embedding the XML PO into my page:
    http://oracle-hack.blogspot.co.uk/2012/04/launching-xml-publisher-from-oa.html
    Could you please help why I am getting error while extending region.
    Thank you,
    Ramu

    Hi. Could you please tell me how did you make it work. I read and try the same document at ttp://oracle-hack.blogspot.co.uk/2012/04/launching-xml-publisher-from-oa.html
    But I got null point exception at one of xdo package which is Oracles own class. I think something is wrong or forgotten in this document.
    Berkay

  • Array to spreadsheet string - remove space after delimiter

    Hi
    I created a Labview program to acquire a electrical signal and send it using TCP/IP.
    The image in attachment shows a piece of my code. The AQ subVI was created by me to accomplish the acquisition.
    However, the string that the "array to spreadsheet string" VI returns is something like this:
    -0.800781^ -1.030273^ -1.098633^ -0.942383^ -0.644531^ -0.209961^ 0.258789^ 0.712891^
    The VI is using the ^ character as a delimiter and it is converting commas to points as decimal separators.
    Now, what i would like to do is to remove the space character between the ^ character and the sample value, simply because that is what the receiver of the TCP/IP message wants.
    Can anybody help me?
    Thanks in advance
    Attachments:
    Array to spreadsheet.png ‏7 KB

    hi there
    remove the space between the ";" and "%" in your format specifier.
    Best regards
    chris
    CL(A)Dly bending G-Force with LabVIEW
    famous last words: "oh my god, it is full of stars!"

Maybe you are looking for