Ora-00907 error

My query is like this :--
select * from incident inc
inner join injuryincident inj on inc.docid=inj.docid where
inc.incdate = (1=decode( :date1 ,null,1,0) or inc.incdate= :date1)
while if it is other field except date it is working fine. Kindly suggest me

SELECT INCDATE
FROM incident
WHERE INCDATE between (1=decode( :date1 ,null,1,0)
) or TO_DATE(:date1,'dd-mm-yyyy')) AND (1=decode(
:date2 ,null,1,0) or TO_DATE(:date2,'dd-mm-yyyy'))
i have tried this also i am getting same errorI would code it as follows, choose a minimum and maximum date where you can be sure that your actual dates are in between
SELECT INCDATE
FROM   incident
WHERE  INCDATE between TO_DATE(NVL(:date1, '01-01-1900'),'dd-mm-yyyy') AND TO_DATE(NVL(:date2, '31-12-2999'),'dd-mm-yyyy')Message was edited by:
Jens Petersen

Similar Messages

  • ORA-0907 error when querying XMLDB Table using XMLExists

    Hi All,
    Get ORA-00907 error when trying to use XMLExists:
    SELECT *
    FROM tnmab_agreement_xml_binary A
    WHERE
    ( XMLExists('declare default element namespace "http://com.oocl.schema.tnm.agreementbuilder"; $XML/Agreement/ShippingPartyGroups/ShippingParties/CustomerHolder[SAP_ID="$ARG"]')
    passing agreements.AGREEMENT_XML as "XML", '5000003001' as "ARG")
    OR
    ( XMLExists('declare default element namespace "http://com.oocl.schema.tnm.agreementbuilder"; $XML/Agreement/NamedCustomerGroups/NamedCustomer/SAP_IDs/StringWrappers[Value="$ARG"]')
    passing agreements.AGREEMENT_XML as "XML", '5000003001' as "ARG")
    ORA-00907: missing right parenthesis
    *00907. 00000 - "missing right parenthesis"*
    **Cause:*
    **Action:*
    Error at Line: 6 Column: 176
    Any help is appreciated
    Thanks
    Auro

    XMLExists('declare default element namespace "http://com.oocl.schema.tnm.agreementbuilder"; $XML/Agreement/ShippingPartyGroups/ShippingParties/CustomerHolder[SAP_ID="$ARG"]'
    passing agreements.AGREEMENT_XML as "XML", '5000003001' as "ARG")no ')' after the closing quote

  • ORA-00907: missing right parenthesis when using group by clause with xmlagg

    I have the following query and I am getting ORA 00907 Error when I am using group by clause with the xmlagg function.
    select xmlelement("Mitigation",
                    xmlelement("m_szMethodName",tm.DisplayName),
                    xmlelement("SubstanceInterferenceProtocolList",
                                (select xmlagg(xmlelement("MitigationProtocol",
                                        xmlelement("m_szMethodName",tm.DisplayName),
                                        xmlelement("m_szInterferenceProtocolName",tmp.protocol_name),
                                        xmlelement("m_szInterferenceSubstance",tmp.intf_mtrl_prod_code),
                                        xmlelement("m_ProtocolParameters",
                                            xmlelement("m_szProtocolName",tmp.protocol_name),
                                                xmlelement("m_Consumables",
                                                    xmlelement("Consumable",
                                                        xmlelement("m_szConsumId", xrl.rgnt_pack_name),
                                                        xmlelement("m_szProductCode",xrl.pack_prod_code),
                                                        xmlelement("m_nVolume",tmp.fluid_vol),
                                                        xmlelement("m_szProtocolStep",xps.protocol_step_name))),
                                                    xmlelement("m_ProtParamList",
                                                        xmlagg(
                                                        xmlelement("ParameterValues",
                                                            xmlelement("m_szProtocolName",tmp.protocol_name),
                                                            xmlelement("m_Time",xpsd.parameter_ntime_value))
                                                        group by tmp.ccd_test_id,tmp.intf_mtrl_prod_code)
                    order by tmp.ccd_test_id, tmp.intf_mtrl_prod_code, xps.protocol_step_intprotocolstep )
                    from XPR_tdef_mitigation_protocol tmp, xp_reagentlist xrl,
                    xpr_protocol_settings xps, xpr_protocol_settings_default xpsd
                    where tmp.ccd_test_id = tm.ccd_test_id
                    and tmp.ccd_test_id = xrl.ccd_test_id
                    and tmp.pack_prod_code = xrl.pack_prod_code
                    and tmp.intf_type = 1
                    and xps.protocol_name = xpsd.protocol_name
                    and xps.protocol_step_name = xpsd.protocol_step_name
                    and xps.ps_action_parameterlist = xpsd.ps_action_parameterlist
                    and xps.protocol_name =  tmp.PROTOCOL_NAME
    from XPtoXPRTdef_defn_mapping tm
    where tm.DisplayName = 'SYPH'If I remove the xmlagg clause along with the group by clause, the query runs fine and give me the output.
    But in that XML format of the output is incorrect for my application.
    Could someone help here?

    Hi,
    userAtoZ wrote:
    I have the following query and I am getting ORA 00907 Error when I am using group by clause with the xmlagg function.
    ... xmlagg(
    xmlelement("ParameterValues",
    xmlelement("m_szProtocolName",tmp.protocol_name),
    xmlelement("m_Time",xpsd.parameter_ntime_value))
    group by tmp.ccd_test_id,tmp.intf_mtrl_prod_code)Please don't post unformatted code. When posting any formatted text on this site, type these 6 characters:
    \(small letters only, inside curly brackets) before and after each section of formatted text, to preserve spacing.
    If the code above were formatted well, so that you could match each '(' with its closing ')', it would look something like this:... xmlagg ( xmlelement ( "ParameterValues"
                        , xmlelement ( "m_szProtocolName"
                                       , tmp.protocol_name
                        , xmlelement ( "m_Time"
                                       , xpsd.parameter_ntime_value
    group by tmp.ccd_test_id
                        ,     tmp.intf_mtrl_prod_code
    This is exactly what you posted, only the whitespace has been changed.
    This makes it clear that the GROUP BY is inside the parentheses with the argument to XMLAGG.  You can have an ORDER BY clause there, but not a GROUP BY clause.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

  • 'Order By' in Exists / Not Exists condition causing ORA-00907 in Apex4.1.1

    Hi Guys,
    We have just upgraded from apex 3.2.1 to 4.1.1. on Oracle DB V11.2.0.1, while testing the apps in apex, I come across this problem.
    When I have a page process that has a condition defined.
    When Condition Type is Exists (SQL query returns at least one row) or Not Exists (SQL query returns no rows) and the Expression 1 is a query with an 'Order By' clause, e.g.
    SELECT 123 FROM DUAL
    ORDER BY 1
    When the process is triggered, Apex 3.2.1 would evaluate the condition and run the process just fine, however Apex 4.1.1 would throw an error : ORA-00907: missing right parenthesis
    I totally understand that an Order by clause in an Exists or Not Exists condition is unnecessary and agree that they shouldn't be there in the first place.
    But unfortunately I am dealing with other developers codes and these conditions have been coded like these, probably from copy & paste codes.
    Saying that, I also believe that an Apex upgrade should not stop anything that is working in previous releases without warning or provide a workaround, right?
    I don't know if this affects other types of artifacts that can have a condition in apex when upgrading from 3.2.1, e.g Regions/Items/Computations/Validations etc.
    Does anyone else get this behaviour? and is there an easy solution to fix these?
    Ideally I don't want to go through all processes (and whatever other artifacts might be affected too) in all apps in all workspaces to check the condition type and remove the 'Order By' clause manually.
    Thanks for any advises
    Just did some more testing
    'Computation' , 'Validations', 'Processes' and 'Branches' have the same problem, 3.2.1 takes 'Order By' fine in Exists/Not Exists condition, but 4.1.1 throws error.
    'Regions', 'Buttons', 'Items' have consistent behaviour - both 3.2.1 and 4.1.1 throw error ORA-00907: missing right parenthesis, when page is rendered.
    Edited by: Danny on 25/04/2012 20:07

    Hi Danny,
    that's interesting. I just had a look what happens when you use an EXISTS or NOT EXISTS condition type. The following final SQL statement will be generated with your above example. You can also see that if you run your application in debug mode.
    select count(*) from sys.dual where exists (select 123 from dual order by 1)Executing that statement in SQL*Plus will also show the ORA-00907 error. It appears that the SQL parser doesn't allow an order by clause in an EXIST clause.
    I wonder why this should have worked in previous versions, but I can only suspect that in the past we may just have executed
    select 123 from dual order by 1which can be slightly slower because with the new EXISTS statement the SQL engine can stop processing earlier if it finds a record.
    We try to be backward compatible as much as possible, but I doubt that we will change that back to the way it was before because of the performance penalty 99.9% of our customers would face.
    Possible Workaround: You might be able to use the new "Application Search" to scan your application for "order by" and fix it for all hits where the attribute name is "Expression 1".
    Regards
    Patrick
    My Blog: http://www.inside-oracle-apex.com
    APEX Plug-Ins: http://apex.oracle.com/plugins
    Twitter: http://www.twitter.com/patrickwolf

  • ORA-00907 Missing right parenthesis? Buh?

    Alright, so I've got this bit of PL/SQL code....
    <i><font face="verdana" size="-1" color="#005F4B">declare
    popname_first VARCHAR2(4000);
    popname_second VARCHAR2(4000);
    poppage_first VARCHAR2(16);
    poppage_second VARCHAR2(16);
    begin
    select rname into popname_first from (select reportname rname from dms_occurances order by occurances desc) where rownum = 1;
    select rname into popname_second from (select reportname rname from dms_occurances order by occurances desc) where rownum = 2;
    select pn into poppage_first from (select pageno pn from dms_occurances order by occurances desc) where rownum = 1;
    select pn into poppage_second from (select pageno pn from dms_occurances order by occurances desc) where rownum = 2;
    </font></i>
    ....and a range of htp.print statements after that.
    The problem is that I'm getting a ORA-00907 error telling me I'm missing my right parenthesis on line 11 (the first of the select assignment lines). Obviously this is not the case. I suspect it has something to do with the way I'm doing the query, but I can't think of any other method for it.
    Please help!

    Are you aware that the predicate 'WHERE/AND ROWNUM = 2' will return exactly zero rows?

  • Alter table returns ORA-00907

    Hi all,
    The following instruction, in an update script provided by a software editor, returns me a ORA-00907 error (missing right parenthesis) :
    alter table TABLE_NAME add C1 VARCHAR2(10 byte) ;
    I ran it on a 8i database.
    If I remove the "byte" between parenthesis, the scripts runs OK.
    What is the "byte" option for ?
    Is it only available from 9i version for example ?
    thanks for your help
    Antoine

    I think it is from 10g onwards only (not sure though).
    It means the size of the column is specified in bytes instead of characters. In 8i there is no difference, but in 10g you can/should use multibyte charsets like AL32UTF8.
    That simply means certain characters need more than one byte to store it (Euro-Sign for example). It would not be possible to add 10 Euro-Signs to your VARCHAR2(10 byte) column, but it would work with a VARCHAR2(10 char) column.
    This explanation is not very good, a better one can be found in the [url http://download.oracle.com/docs/cd/B19306_01/server.102/b14225/ch6unicode.htm#CACHJHDJ]Oracle 10 Globalization Guide
    Just remove the "byte" from the script and you are doing fine.

  • Using DBMS_METADATA.GET_DDL get error: ORA-00907: missing right parenthesis

    Hi,
    I'm trying to extract schema DDL from a database (10.2.0.4.0 - 64bit Enterprise Edition on Solaris 10). I run the query below and get an ORA-00907: missing right parenthesis error.
    SELECT DBMS_METADATA.GET_DDL( REPLACE(object_type,' ','_') AS object_type, object_name) FROM user_objects WHERE object_type NOT IN ('TABLE_PARTITION','INDEX_PARTITION','LOB');
    This is the output when running the above in sqlplus worksheet
    select DBMS_METADATA.GET_DDL( REPLACE(object_type,' ','_') as object_type, object_name) FROM user_objects where object_type not in ('TABLE_PARTITION','INDEX_PARTITION','LOB')
    ERROR at line 1:
    ORA-00907: missing right parenthesis
    removing the where clause gives the following:
    select DBMS_METADATA.GET_DDL( REPLACE(object_type,' ','_') as object_type, object_name) FROM user_objects
    ERROR at line 1:
    ORA-00907: missing right parenthesis
    Any pointers would be gratefully received. I know I could get the DDL out using exp/imp but I want to understand why I'm getting the missing parenthesis error.
    cheers,
    Ewan

    SELECT DBMS_METADATA.GET_DDL( REPLACE(object_type,' ','_') AS object_type, object_name) FROM user_objects WHERE object_type NOT IN You don't need an alias here. Get rid of " AS object_type" and it should work.

  • FOR UPDATE on scrollable cursor and error: ORA-00907: missing right parenthesis

    If change my query to have a FOR UPDATE and make it an updatable scrollable cursor I get an error on the updateRow() command saying "ORA-00907: missing right parenthesis"
    If I remove the FOR UPDATE it works OK.
    The problem I have is trying to update a CLOB from a ResultSet. If I do not upate any other column I get the error saying that the error"
    "ORA-22920: row containing the LOB value is not locked"
    I can get around this by adding FOR UPDATE. But if I add FOR UPDATE and try to update any non-CLOB column I get the 00907 error above.
    Hmmmm. So here is what I can and cannot do:
    - I CAN update the CLOB IF I update another column 1st and NO FOR UPDATE clause.
    - I CAN update the CLOB only if I have FOR UPDATE clause.
    - I CANNOT update just the CLOB without FOR UPDATE.
    - I CANNOT update any non-CLOB column with FOR UPDATE.
    What a pain in the ***! How am I to provide generic access to the applications being built on my DB layer. This is crazy!

    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Andrew Edgar ([email protected]):
    I have this same problem!
    The error occurs when performing updateRow.
    The turning off of auto commit only gets the query to work but not the actual update.
    Will this be fixed in the next version of the Driver?<HR></BLOCKQUOTE>
    Here is the stack Trace I recieved:
    java.sql.SQLException: ORA-00907: missing right parenthesis
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:168)
    at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:208)
    at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:543)
    at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1405)
    at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteFetch(TTC7Protocol.java:822)
    at oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java:1446)
    at oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java:1371)
    at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1900)
    at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:363)
    at oracle.jdbc.driver.UpdatableResultSet.execute_updateRow(UpdatableResultSet.java:2135)
    at oracle.jdbc.driver.UpdatableResultSet.updateRow(UpdatableResultSet.java:1322)

  • Error in form ora- 00907

    hi all
    i have work in the oracle form and genrating the dynamic query in the pl/sql block and to accessing in the remote so use the statemet
    dbms_sql.parse(src_cur, str,1);
    st_cur is cursor define
    str is my string pass;
    1 insad of dbms_sql.native bas in the remote data are access
    way is error is give and what is the solutaion.
    help
    thanks;

    Could you list the exact code you are using as the error is:
    ORA-00907: missing right parenthesis
    Cause: A left parenthesis has been entered without a closing right parenthesis, or extra information was contained in the parentheses. All parentheses must be entered in pairs.

  • FOR UPDATE on updatable cursor and error: ORA-00907: missing right parenthesis

    Anyone run into this? I've searched the message board and bug db to no avail.
    - Using latest Oracle JDBC 2.0 compliant "thin" driver and Oracle 8.1.6 database.
    1) Using prepareStatement specifying an updatable cursor for something like "SELECT FNAME,LNAME FROM USERS FOR UPDATE OF FNAME,LNAME"
    2) Updating FNAME using updateString("FNAME","whatever"), and then calling updateRow() of the ResultSet yields:
    ORA-00907: missing right parenthesis
    If I remove the FOR UPDATE clause then everything works just fine.
    Workarounds/suggestions appreciated!
    Thanks,
    Ryan
    null

    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Andrew Edgar ([email protected]):
    I have this same problem!
    The error occurs when performing updateRow.
    The turning off of auto commit only gets the query to work but not the actual update.
    Will this be fixed in the next version of the Driver?<HR></BLOCKQUOTE>
    Here is the stack Trace I recieved:
    java.sql.SQLException: ORA-00907: missing right parenthesis
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:168)
    at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:208)
    at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:543)
    at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1405)
    at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteFetch(TTC7Protocol.java:822)
    at oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java:1446)
    at oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java:1371)
    at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1900)
    at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:363)
    at oracle.jdbc.driver.UpdatableResultSet.execute_updateRow(UpdatableResultSet.java:2135)
    at oracle.jdbc.driver.UpdatableResultSet.updateRow(UpdatableResultSet.java:1322)

  • Error ORA-00907 with query  SDO_GEOM.SDO_DIFFERENCE

    Hi,
    I have following query:
    SELECT SDO_GEOM.SDO_DIFFERENCE(
    SDO_RELATE(square.geometry, SDO_GEOM.SDO_BUFFER(MDSYS.SDO_GEOMETRY(3001, 1, MDSYS.SDO_POINT_TYPE(424, 1272, 0) , NULL, NULL), 100, 0.05,'unit=m arc_tolerance=0.005'), 'mask=ANYINTERACT querytype=WINDOW') = 'TRUE',
    SDO_RELATE(square.geometry, SDO_GEOM.SDO_BUFFER(MDSYS.SDO_GEOMETRY(3001, 1, MDSYS.SDO_POINT_TYPE(276, 1274, 0) , NULL, NULL), 100, 0.05,'unit=m arc_tolerance=0.005'), 'mask=ANYINTERACT querytype=WINDOW') = 'TRUE',
    0.001
    Always get the ora-00907: a bracket is missing-error.
    Any help is really appreciated. Is there a error in the query?
    Regards Ronald.

    Hi Ronald,
    try following:
    SELECT SDO_GEOM.SDO_DIFFERENCE(
        SELECT square.geometry from square where
          SDO_RELATE (square.geometry, SDO_GEOM.SDO_BUFFER(
              MDSYS.SDO_GEOMETRY(
                3001, 1, MDSYS.SDO_POINT_TYPE(424, 1272, 0) , NULL, NULL
              ), 100, 0.05,'unit=m arc_tolerance=0.005'
            ), 'mask=ANYINTERACT querytype=WINDOW'
          ) = 'TRUE'
        SELECT square.geometry from square where
          SDO_RELATE (square.geometry, SDO_GEOM.SDO_BUFFER(
              MDSYS.SDO_GEOMETRY(
                3001, 1, MDSYS.SDO_POINT_TYPE(276, 1274, 0) , NULL, NULL
              ), 100, 0.05,'unit=m arc_tolerance=0.005'
            ), 'mask=ANYINTERACT querytype=WINDOW'
          ) = 'TRUE'
        0.001   
    FROM DUAL   

  • OraOLEDB.Oracle GetRecordSet() throw "ORA-00907: missing right parenthesis"

    Hi,
    I am unfortunately working on an old VB6 app that is constructing a huge (11902 characters) ad-hoc SQL statement which is then passed to the GetRecordSet() method of my DBConnection. The app is using the OraOLEDB.Oracle provider. When the GetRecordSet() method is executed, however, I get the following error:
    ORA-00907: missing right parenthesis
    Now I have grabbed the contents of the string that is passed in to the GetRecordSet() function and have thoroughly examined it and there are no missing parens. Additionally, I am able to execute the select statement in Oracle SQL Developer as well as SQL*Plus, withou difficulty. So I am sure that the string is syntactically correct.
    I am beginning to suspect that something fishy is happening in the provider - perhaps the string is too long and it is getting truncated somewhere?
    Can anyone out there help me out?
    Thanks, Steve

    maybe the conversion you are trying to do is not valid especially in the first one into binary(1).
    check out the conversion table for CAST operator in the SQL REFERENCE of the documentation.

  • Trying to use authorization schema but getting ORA-00907: missing right par

    Hi,
    I am fairly new to HMTLDB. I am busy going through the Issue Tracker Tutorial. I am on the last part of Tutorial. This part involves authorizing a user based on their roles in the company.
    I now keep getting the following when I load my pages
    ORA-00907: missing right parenthesis
    Error ERR-1082 Error in executing authorization scheme code.
    How do I go about debugging this error not sure where to start?

    if this helps I am using this PDF
    http://www.oracle.com/technology/products/database/application_express/pdf/issue_tracking_tutorial_1.6_0.pdf
    if you open the PDF file I am stuck on page 72-74. The page I am trying to open while i am logged on as FUNKYMONKEY is Page 4 which is in the documentation

  • ORA-00907 MISSING RIGHT PARANTHESIS

    Dear all,
    The query
    FLASHBACK TABLE schema.table_name TO TIMESTAMP('18-JAN-2008 18:55:58','DD-MON-YYYY HH24:MI:SS');
    gives me the error
    ORA-00907 MISSING RIGHT PARANTHESIS
    WHAT AM MISSING HERE ?
    kAI

    Pretty much the usual
    You grossly violate forums etiquette by
    - not posting a version and a platform
    - not looking up the error message
    - not verifying syntax
    - by SHOUTING most of your question
    in short you demonstrate you are utterly lazy and utterly rude.
    Doing so, you have now entered as a runner up in the competition to qualify for the biggest abuser of this forum by not doing anything yourself.
    Yes, I know you will be angry. And why will you be angry? Because I state the truth!
    People like you should be banned from this forum completely.
    Sybrand Bakker
    Senior Oracle DBA

  • ORA-00907: missing right parenthesi

    hello,
    hi, i am having a problem with creating a temporary table
    create global temporary table tt_My0
    id NUMBER(10,5) DEFAULT NULL,
    NAME VARCHAR2(40) DEFAULT NULL,
    )but its giving an error
    ORA-00907: missing right parenthesisi guess, its giving me that error cause it is considering field-name NAME as a keyword..
    so how can i cop up that error
    thank you..

    it worked here ,i jusr removed a comma.
       create global temporary table tt_My0
    id NUMBER(10,5) DEFAULT NULL,
    NAME VARCHAR2(40) DEFAULT NULL            -----removed comma
    )Hope it helps,
    CKLP
    Edited by: CKLP on Apr 5, 2011 10:26 PM

Maybe you are looking for

  • Configurations done at SAP gui level to print in duplex mode

    Hi Gurus, We had a requirement to convert a printer to duplex mode, we changed all the settings at SAP level( kept duplex mode in printing mode and changed device type to SWAN (as post and pre2 device types are not available) ). But still we are not

  • Activity group in the tolerance limit

    Hi experts, I have a question related to 'Define Tolerence limits of the availability control'. I hope someone can help me with this. My doubt is related to how activity groups works in this settings. For example : If i had a tolerence limit for all

  • Can't open WMV files in Quicktime. How can I reinstall Quicktime?

    For some reason I am unable to open WMV files in Quicktime even though I have Flip4Mac Player Pro (WMV files played fine in Quicktime until recently). ANY help would be GREATLY appreciated!

  • RS232 communicat​ion with cDAQ

    Hello, I am about to commence a project which will require my LabVIEW application to communicate with an RS232 device.  I am planning on using an Ethernet 4-slot Compact DAQ module, but can't see a way to connect through. Is this possible? Is there a

  • Error -201 buying songs from ITunes: download fails

    Not able to buy songs on an album from ITunes. Download fails, err = -201. Is ITunes failing on album purchases for anyone else? V 7.2 on Win XP Pro.