Problem in timestamp

I am working on opensource project and i am buiding it from source.
it will work on jdk1.5 and orackle 10g, when i am buindling, i am getting error of timestamp as:
"reference to Timestamp is ambiguous, both class java.sql.Timestamp in java.sql a
nd class java.security.Timestamp in java.security match
[javac] Timestamp ConvDate, String RateType, int AD_Client_ID, i
nt AD_Org_ID)"
first I tried with jdk5.0 as in the sun site in compatbility it is given timestamp function is removedin jdk5.0, and j2se5.0 is having that function.so I tried with it but I am getting the same error.
How can I include Timestamp function in j2se, so that i can over come this problem.plz help me out.

what's the datatype for the column? If it is a TIMESTAMP, you get the zero's for free. You can't remove them... when you don't want to display them, use TO_CHAR (as Boneist showed you)
SQL> create table t
  2  (x timestamp)
  3  /
Table created.
SQL> insert into t
  2  values (systimestamp)
  3  /
1 row created.
SQL> ed
Wrote file afiedt.buf
  1  insert into t
  2* values (to_date ('12-nov-2007 10:00:00', 'dd-MON-yyyy hh24:mi:ss'))
SQL> /
1 row created.
SQL> select *
  2    from t
  3  /
X
12-NOV-07 03.50.13.312000 PM
12-NOV-07 10.00.00.000000 AM
SQL> select to_char (x, 'dd-mon-yyyy hh24:mi:ss')
  2    from t
  3  /
TO_CHAR(X,'DD-MON-YYYYHH24
12-nov-2007 10:00:00
SQL> Message was edited by:
Alex Nuijten

Similar Messages

  • Problem with timestamp in query

    I have problem with timestamp in JPA query.
    I wonna select all data from database where difference between two timestamps is more than 3 month.
    Database:
    ID timestamp1 timestamp2
    1 20008-11-19 15:02000 20008-08-19 15:02000
    2 20008-11-19 15:02000 20008-11-14 15:02000
    @Column(name = "timestamp1", nullable = false)
    @Temporal(TemporalType.TIMESTAMP)
    public Date timestamp1;
    @Column(name = "timestamp2", nullable = false)
    @Temporal(TemporalType.TIMESTAMP)
    public Date timestamp2;
    sql query works:
    select id from table where
    MONTH( DATE(timestamp1) - DATE(timestamp2) ) > 3
    but how I can write in Java?
    I't doesnt wrk:
    Query query = em.createQuery("SELECT f.id FROM Foo f WHERE MONTH( DATE(f.timestamp1) - DATE(f.timestamp2) ) > 3 ")
    error:
    ExceptionUtil E CNTR0020E: EJB threw an unexpected (non-declared) exception during invocation of method .
    Exception data: <openjpa-1.0.2-r420667:627158 nonfatal user error> org.apache.openjpa.persistence.ArgumentException: An error occurred while parsing the query filter 'SELECT f.id FROM Foo f WHERE MONTH( DATE(f.timestamp1) - DATE(f.timestamp2) ) > 3'.
    Error message: <openjpa-1.0.2-r420667:627158 nonfatal user error> org.apache.openjpa.kernel.jpql.ParseException: Encountered "MONTH (" at character 438, but expected: ["(", "+", "-", ".", ":", "", "=", "?", "ABS", "ALL", "AND", "ANY", "AS", "ASC", "AVG", "BETWEEN", "BOTH", "BY", "CONCAT", "COUNT", "CURRENT_DATE", "CURRENT_TIME", "CURRENT_TIMESTAMP", "DELETE", "DESC", "DISTINCT", "EMPTY", "ESCAPE", "EXISTS", "FETCH", "FROM", "GROUP", "HAVING", "IN", "INNER", "IS", "JOIN", "LEADING", "LEFT", "LENGTH", "LIKE", "LOCATE", "LOWER", "MAX", "MEMBER", "MIN", "MOD", "NEW", "NOT", "NULL", "OBJECT", "OF", "OR", "ORDER", "OUTER", "SELECT", "SET", "SIZE", "SOME", "SQRT", "SUBSTRING", "SUM", "TRAILING", "TRIM", "UPDATE", "UPPER", "WHERE", <BOOLEAN_LITERAL>, <DECIMAL_LITERAL>, <IDENTIFIER>, <INTEGER_LITERAL>, <STRING_LITERAL>].
    at org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder$ParsedJPQL.parse(JPQLExpressionBuilder.java:1665)
    at org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder$ParsedJPQL.<init>(JPQLExpressionBuilder.java:1645)

    The error is indocating improper formatting of your JPQL string. MONTH is not understood. I would recommend using your SQL string in a createNativeQuery(...) call instead.
    Doug

  • Strange problem with timestamps

    Hi
    I don't think this is a bc4j problem, but maybe someone can give me a hint anyway...
    What would you expect the following code to print:oracle.jbo.domain.Timestamp ts = new oracle.jbo.domain.Timestamp("0000-02-03 11:12:59");
    System.out.println(ts);I guess you would expect something like "0000-02-03 11:12:59", would you? But this code prints "0001-02-03 11:12:59". Note that the year has silently been changed from 0000 to 0001. It is getting even more strange if you look at the following codeoracle.jbo.domain.Timestamp ts = new oracle.jbo.domain.Timestamp("0001-02-03 11:12:59");
    System.out.println(ts);This code prints just the same as the first example: "0001-02-03 11:12:59".
    To say the truth I'd have expected everything, but not that years are silently converted to other years without any notification or exceptions.
    Has anyone a clue what is happening here?
    Thanks
    Frank Brandstetter

    In my opinion it's simply logic:
    The first day, the first month , the first year is 0001-01-01.
    The zero year doens't exists.
    Regards
    Fred

  • Problems with timestamps

    Hello everybody,
    and here is my problem for this day ;-).
    I am trying to use a timestamp which comes from an database entry.
    The data type in the database is timestamp and the entries are looking
    like this 2002-06-19 09:22:19.238805. My question is now
    how to use this timestamp in Java. I have tried to use new Timestamp(..) so far, but either I use the deprecated constructor or a constructor with the timestamp in milliseconds after 1970. But I don't have the milliseccons and using the first mentioned constructor isn't that productiv.
    It would be perfect if I could use the generated date for a date navigator as well.
    Has anyone a solution?
    Best regards
    Joachim

    Hi,
    In database it will always display you as a String you told,  but when you fetch it the return type will always be java.sql.TimeStamp or java.sql.Date.
    so You can use the my method of using it.
    Otherwise you have to read the strings and create the date... which a wrong way of doing it ,because all methods are deprecated.
    REgards,
    Praveen

  • File Synch problem with timestamp

    Win2k, LabVIEW 7.0
    I'm trying to do file synchronization between the data files I produced on the local disk, and a remote server.
    I am doing a LIST FILES on the local folder, and a LIST FILES on the remote folder.
    For each file, I do a GET FILE INFO, and look at the LAST MOD data (a TIMESTAMP value).
    For each file in the SOURCE folder, I match it up with the corresponding entry in the DESTINATION folder.
    I then compare the times, and if the SOURCE timestamp is greater than the DEST timestamp, then I delete the DEST file, and COPY the source file to the DEST.
    There are a few files that fail this process, though, and I am puzzled as to why.
    If I look (via Windows explorer) at the properties of one of these files, it says the LAST MOD date is 6:09:20. That is the case for BOTH the local copy and the remote copy.
    However, the SYNCH logic above insists on copying this file every time it runs. When I add logging stuff to the synch process, it tells me that the local file has a date of 6:09:21, and the remote file has a date of 6:09:20, so it wants to copy it.
    But after the copy, things are exactly the same - Windows shows the times identical, but LabVIEW shows them ONE second apart, and copies them AGAIN the next time it runs. This is true for about 6 files out of a folder of 50-60. I suppose I could allow for that one second, if I knew why it was there.
    What's biting me here? If the file really had a MOD DATE resolution of 1 mSec say, then I could understand that maybe the PROPERTIES window truncates the value, and the TIMESTAMP does not. But even then, it ought to copy ONCE and set them the same...
    The "Server" I am testing on is running OSX, 10.4.6, if that matters.
    What am I missing?
    Steve Bird
    Culverson Software - Elegant software that is a pleasure to use.
    Culverson.com
    Blog for (mostly LabVIEW) programmers: Tips And Tricks

    CoastalMaineBird wrote:
    Win2k, LabVIEW 7.0
    I'm trying to do file synchronization between the data files I produced
    on the local disk, and a remote server.
    I am doing a LIST FILES on the local folder, and a LIST FILES on the
    remote folder.
    For each file, I do a GET FILE INFO, and look at the LAST MOD data (a
    TIMESTAMP value).
    For each file in the SOURCE folder, I match it up with the
    corresponding entry in the DESTINATION folder.
    I then compare the times, and if the SOURCE timestamp is greater than
    the DEST timestamp, then I delete the DEST file, and COPY the source
    file to the DEST.
    There are a few files that fail this process, though, and I am puzzled as to why.
    If I look (via Windows explorer) at the properties of one of these
    files, it says the LAST MOD date is 6:09:20. That is the case for BOTH
    the local copy and the remote copy.
    However, the SYNCH logic above insists on copying this file every time
    it runs. When I add logging stuff to the synch process, it tells me
    that the local file has a date of 6:09:21, and the remote file has a
    date of 6:09:20, so it wants to copy it.
    But after the copy, things are exactly the same - Windows shows the
    times identical, but LabVIEW shows them ONE second apart, and copies
    them AGAIN the next time it runs. This is true for about 6 files out of
    a folder of 50-60. I suppose I could allow for that one second, if I
    knew why it was there.
    What's biting me here? If the file really had a MOD DATE resolution of
    1 mSec say, then I could understand that maybe the PROPERTIES window
    truncates the value, and the TIMESTAMP does not. But even then, it
    ought to copy ONCE and set them the same...
    The "Server" I am testing on is running OSX, 10.4.6, if that matters.
    What am I missing?
    It
    is a file system issue. NTFS uses something like a 100nSec resolution
    but historically the FAT file times have had a two second resolution.
    Apparently the Property dialog does convert the timestamp to a DOS time
    all the time before displaying it.
    Your MacOSX system uses a completely different resolution (at least 1
    sec but probably better). The network protocol does allow for high
    resolution transmissions and so the exact time gets transmitted but
    somehow your local system has a DOS limitation for the harddisk volume
    in question so that LAbVIEW returns the DOS time too for the local
    volume. The Explorer property dialog will always show DOS time only it
    seems, I had similar issues in the past but didn't really dig deeper,
    just accepted the 1 second difference.
    Rolf Kalbermatter
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • File Synchronization problem with TimeStamp

    Win2k, LabVIEW 7.0
    I'm trying to do file synchronization between the data files I produced on the local disk, and a remote server.
    I am doing a LIST FILES on the local folder, and a LIST FILES on the remote folder.
    For each file, I do a GET FILE INFO, and look at the LAST MOD data (a TIMESTAMP value).
    For each file in the SOURCE folder, I match it up with the corresponding entry in the DESTINATION folder.
    I then compare the times, and if the SOURCE timestamp is greater than the DEST timestamp, then I delete the DEST file, and COPY the source file to the DEST.
    There are a few files that fail this process, though, and I am puzzled as to why.
    If I look (via Windows explorer) at the properties of one of these files, it says the LAST MOD date is 6:09:20. That is the case for BOTH the local copy and the remote copy.
    However, the SYNCH logic above insists on copying this file every time it runs. When I add logging stuff to the synch process, it tells me that the local file has a date of 6:09:21, and the remote file has a date of 6:09:20, so it wants to copy it.
    But after the copy, things are exactly the same - Windows shows the times identical, but LabVIEW shows them ONE second apart, and copies them AGAIN the next time it runs. This is true for about 6 files out of a folder of 50-60. I suppose I could allow for that one second, if I knew why it was there.
    What's biting me here? If the file really had a MOD DATE resolution of 1 mSec say, then I could understand that maybe the PROPERTIES window truncates the value, and the TIMESTAMP does not. But even then, it ought to copy ONCE and set them the same...
    The "Server" I am testing on is running OSX, 10.4.6, if that matters.
    What am I missing?
    Steve Bird
    Culverson Software - Elegant software that is a pleasure to use.
    Culverson.com
    Blog for (mostly LabVIEW) programmers: Tips And Tricks

    So every time you store a file with an uneven number of seconds it will loose the last bit and become even
    That's not the case. If you read the real thread (I'm not sure how this got posted here, though I know I'm responsible), you'll see that I found cases where it rounded(?) the time from an even number to an odd number of seconds.
    Steve Bird
    Culverson Software - Elegant software that is a pleasure to use.
    Culverson.com
    Blog for (mostly LabVIEW) programmers: Tips And Tricks

  • Problem with Timestamp

    Hi
    I am using Oracle 10.1.0.4. When I am storing events with the received
    timestamps, it stores in GMT. But I am calling the stored procedure
    with timestamp in IST. Similarly when I search for that using IST, It
    returns the results matching the corresponding GMT. If I search 6.30 AM
    IST, It returns results for 1.00 AM.
    Appreciate your help

    What kind of timestamp datatype?
    How are timestamps "received" and stored?
    Time zone settings (sessions and database)?
    SQL> drop table tider;
    Table dropped.
    SQL> create table tider (t1 timestamp with time zone, t2 timestamp with local time zone);
    Table created.
    SQL> select sessiontimezone from dual;
    SESSIONTIMEZONE
    -05:00
    SQL> insert into tider values ('1-jul-6 1:0:0 pm','1-jul-6 1:0:0 pm');
    1 row created.
    SQL> select * from tider;
    T1
    T2
    01-JUL-06 01.00.00.000000 PM -05:00
    01-JUL-06 01.00.00.000000 PM
    SQL> alter session set time_zone='Europe/Stockholm';
    Session altered.
    SQL> select * from tider where t1='1-jul-6 8:0:0 pm CET';
    T1
    T2
    01-JUL-06 01.00.00.000000 PM -05:00
    01-JUL-06 08.00.00.000000 PM
    Is this same as what you are seeing?

  • Database toolkit & Oracle 11g, problem with timestamps

    I tested my application, based on the Database toolkit, with Access and Oracle XE (10g) databases and all was ok. After moving my database to a Oracle 11g server, i get this error for any query involving a TIMESTAMP WITH TIME ZONE or TIMESTAMP WITH LOCAL TIME ZONE column:
    ADO Error: 0x80040E21
    Exception occured in Microsoft OLE DB Provider for ODBC Drivers: ODBC driver does not support the requested properties.
    The error is raised by the "Execute" invoke node in "DB Tools execute query.vi".
    Using Labview 2009 and up to date Oracle ODBC drivers on Windows XP

    Hi SnamProgetti,
    I don't have any useful information about this error. You can try to read this and this document.
    Have a nice day,
    Simone S.
    Academic Field Engineer - Med Region

  • Problems with Timestamp

    Hello everyone!!
    I have a table for work with schedules, that has timestamp's fields. When I enter a time, for example, 09:00, the database save it as 01/01/70 09:00:00.
    I want to use the actual date instead 01/01/70. What can I do?
    Thanks.

    I believe your using java,
    You may get the system date,
    Then use the calender's following method
    void set(int year, int month, int date, int hour, int minute, int second) /*Sets the values for the fields year, month, date, hour, minute, and second. */
    And then :
    long getTimeInMillis()
    Gets this Calendar's current time as a long.
    To create the Timestamp.
    Hope it helps,
    Daniel Campelo

  • Problems with TIMESTAMP Field from SQL Server

    OBIEE 11g
    Hi All,
    I want to convert data into OBIEE that is coming from a TIMESTAMP field in SQL Server Database. So in SQL Server field has data like '9/20/2012 12:05:08 AM'. I have first changed the datatype in physical layer to DATETIME and then in BMM I do a CAST(<DATE_FIELD> AS DATE). On the frontend when I use this column the error I get back is [nQSError: 59030] Illegal data type conversion from source type: VARBINARY to target type: TIMESTAMP. (HY000). Does anyone know a workaround or solution.
    Thanks in Advance!

    Hi Guys,
    None of the solutions you mentioned have worked unfortunately. I have a date column and another column that holds user id. I basically want to do a count of all the user id's where that particular date column is NULL. I have checked in the physical layer and the date column in question is coming from SQL Server as a TIMESTAMP datatype. So I initially did not change anything and brought the column in as is but that did not work out. I then tried to change the datatype in the physical layer to DATETIME and then also DATE. After changing the datatype in the physical layer in the BMM I would do a CAST(<date column> as DATE) and this still did not work. I then tried to just change the datatype to DATETIME and DATE without doing the CAST in the BMM and this still did not work. Not too sure what to do now.

  • Problems passing timestamp variable to block-SQL command not properly ended

    Can you please help me answer or direct me to resources in answering the following.
    I'm attempting to pass a timestamp variable to a block but am getting errors with every method I've tried yet.
    The example below is attempting to generate a list of all sales dates for orders after the 21st of March 2000.
    DECLARE
    BeginDate Orders.PurchaseDate%TYPE :=to_date('21-3-2000', 'dd-mm-yyyy');
    Target Orders.PurchaseDate%TYPE;
    BEGIN
    DBMS_OUTPUT.PUT_LINE(to_char(BeginDate));
    SELECT Distinct PurchaseDate from Orders into Target WHERE PurchaseDate>BeginDate;
    END;
    When running it - it returns
    ORA-00933: SQL command not properly ended ORA-06512: at line 8Please advise

    -- I"m still trying to get a timestamp into an execute immediate statement.
    Declare
    BeginDate Orders.PurchaseDate%TYPE :=to_date('21-3-2000', 'dd-mm-yyyy');
    var_date Orders.PurchaseDate%TYPE ;
    BEGIN
    DBMS_OUTPUT.PUT_LINE(to_char(BeginDate,'DD.MM.YYYY'));
    sql1 = 'SELECT MAX(PurchaseDate) INTO Target from Orders WHERE PurchaseDate> :var_date';
    Execute Immediate sql1 Using BeginDate;
    DBMS_OUTPUT.PUT_LINE(to_char(Target,'DD.MM.YYYY'));
    END;
    Thanks again for the replies, I'm still not there yet even after re-reading the documentation that applies to this,
    Using what follows below the Execute Immediate line/syntax is the problematic part of this...
    to quote the block line still returning errors.
    This line which would seem natural...
    Execute Immediate sql1 Using BeginDate;returns -- missing keyword
    Modified with this line attempts to pass another variable to the block also errors.
    Execute Immediate sql1 Using BeginDate, var_date;returns -- ORA-01006: bind variable does not exist
    Perhaps I'm not getting some key concept here, but I would think passing a variable into execute immediate would be
    as simple as passing a string or int into a *.bat,*.sh file or function/procedure in any other language.
    And/or I'm missing a key element or understanding to how this syntax should work.
    Thank you very much for your previous replies any other ideas welcome.

  • Timestamp conversion problem.

    I work in the development of a LabVIEW program that communicates with a
    server (written in Java). All acquired data is sent via TCP and the
    server can read everything (waveforms and other information). However,
    there is a problem in timestamp conversion. We don't know how to
    convert the milliseconds correctly. The timestamp is inside a waveform,
    so we cannot convert it to formatted string.
    Example:
    Original timestamp:
    13:37:19,639
    11/10/2005
    String generated with "Flatten to String":
    0000 0000 BF71 9ABF A3D7 0800 0000 0000
    Converted value (Java server):
    13:37:19,000
    11/10/2005
    Does anyone know the algorithm to obtain the milliseconds from this value: "A3D7 0800"?
    Thanks for attention.
    My regards,
    Vinicius Falseth
    Solved!
    Go to Solution.

    There is a faster way.  You can extract the timestamp from the waveform using Get Waveform Components. 
    At that point, you can convert it to whatever you want.  Attached
    is a VI which shows a simple conversion to milliseconds, losing a lot
    of resolution (128 bit timestamp goes to 52 bit double) and a more
    complex conversion showing the internal structure of the timestamp (it
    is a 128 bit fixed point number with the decimal in the middle). 
    You can modify the second conversion to do such things as throw away
    the integer portion to get higher resolution on the fraction.  Or
    you could just save to Java using a four-integer structure.
    This account is no longer active. Contact ShadesOfGray for current posts and information.
    Attachments:
    timestamp.llb ‏48 KB

  • Jdbc timestamp error on getting timezone

    Hello
    I changed my application from J2EE standalone container 9.0.4 to the new OAS 10.1.0.2.
    Now I have a problem with timestamp CMP-Attributes.
    When I set a timestamp attribut and get it back I have the following exception. The JDBC driver seems to convert the timestamp variable with a sun util for timezones.
    I allready set the timezone to real value on the database and with -Duser.timezone Options for the VM.
    The Exception is:
    java.lang.IllegalArgumentException
         at sun.util.calendar.ZoneInfo.getOffset(ZoneInfo.java:322)
         at oracle.jdbc.driver.DateTimeCommonAccessor.zoneOffset(DateTimeCommonAccessor.java:370)
         at oracle.jdbc.driver.DateTimeCommonAccessor.getMillis(DateTimeCommonAccessor.java:411)
         at oracle.jdbc.driver.TimestampAccessor.getTimestamp(TimestampAccessor.java:153)
         at oracle.jdbc.driver.OracleResultSetImpl.getTimestamp(OracleResultSetImpl.java:750)
         at com.evermind.sql.ResultSetBCELProxy.getTimestamp(ResultSetBCELProxy.java:297)
         at FaelleLocal_EntityBeanWrapper30.loadStateCorePKNonPartial(FaelleLocal_EntityBeanWrapper30.java:44476)
         at EbenenLocal_FaelleLocal_ORCollection172.getObjects(EbenenLocal_FaelleLocal_ORCollection172.java:93)
         at com.evermind.server.ejb.ORCollection.contains(ORCollection.java:273)
         at com.evermind.server.ejb.ORCollection.add(ORCollection.java:228)
         at com.evermind.server.ejb.ORCollection.add(ORCollection.java:355)
         at FaelleEJB_PersistenceManager31.__core__setebene(FaelleEJB_PersistenceManager31.java:1083)
         at FaelleEJB_PersistenceManager31.setEbene(FaelleEJB_PersistenceManager31.java:1109)
         at FaelleLocal_EntityBeanWrapper30.setEbene(FaelleLocal_EntityBeanWrapper30.java:11182)
         at com.rehabnet.rehabcycle.server.util.TOFactory.setFallTO(TOFactory.java:693)
         at com.rehabnet.rehabcycle.server.impl.ResourceManagerSessionEJB.setFall(ResourceManagerSessionEJB.java:1411)
         at ...
    Thanks for your help.
    best
    chrue

    Hello
    Thanks for your help.
    I solved the problem.
    We changed the column type from date to timestamp.
    While doing this oracle produces illegal timestamp values with negativ milliseconds. When the bean reads the data he convert the time to the java time with the timezone. The IllegalArgumentException was throwing because of the negativ millisecond part.
    best
    chrue.

  • PXI-6682 + multiple Serie S & M cards cause timestamp delay

    I'll try to give as much info as possible and hopefuly someone will have an answer to this problem.
    Language: C++
    Introduction:
    1- I have (1) PXI-6682 (Timing card), (6) PXI-6143 (Serie S (8 analog inputs each)), and (2) PXI-6224 (serie M (8 analog inputs each))
    2- Every card is a task (so that's 8 tasks
    3- Every card is in sync (they give data equal...more or less... to one another
    PROBLEM:
    1- Timestamp is off by up to 200 ms (not drifting...simply off by a set number of ms)
    2- Every call to niSync_ReadMultipleTriggerTimeStamp gives me a timestamp off by that much
    I don't have any info on how the tester managed to know it was 200 ms off, my theory is he tested it with some older equipment to validate the new one

    Hello there,
    Kindly help me with DAQmx Time stamp related problem as described below.
    Setup : PXI 6133 Qty 4 (Slot 3, 4, 5, 6)
    PXI 6255 Qty 1 (Slot 2)
    PXI 6255 doing a Continuous Acquisition at 1 mSec Sampling and 1000 samples/iteration.
    PXI 6133 doing a Ref Triggered Acquisition at 1 uSec Sampling interval and Pre and Post Trigger samples of 100000 Samples each.
    Test : PXI 6133 - Reference Trigger Configured on PFI 1 line of First PXI 6133 card.
                             input Signal given to AI 0 OF First PXI 6133 card.
                             All PXI 6133 cards are included in a single task.
    PXI 6255 - Input given to Channel 0 AI
    External Function generator - One Digital Trigger generated of width 50 mSec High Interval.
                                               Another signal generated for input to above cards. (Square wave of 10 mSec Period - 5 periods generated on the rising edge of trigger)
    So It means When I acquire square wave in my waveform, I can consider rising edge of square wave as a rising edge of trigger (as both signals are generated aligned from external function generator)
    I have attached Screenshots and programs I have used for that.
    Problem: As both singal are generated at a same event, Both 6133 and 6255 should acquire that singnal at a same timestamp.
    I have also read related documents about timestamp but I could not succeeded to find any link in this.
    I am getting square wave 100 msec earlier in 6255 then of 6133.
    If I used only single card of 6133 then that inaccuracy of 100 msec is shifted to 25 msec.
    Please help me as soon as possible.
    Attachments:
    Timestamp mismatch between 6133 and 6255.docx ‏377 KB
    Timestamp mismatch in 6133 & 6255.zip ‏70 KB

  • Problem in loading applets

    HI,
    Im facing a problem when im trying to open a URL containing a applet in IE 7.
    When i checked in the settings of IE the JVM used for loading of applets is java 2 v 1.5.0_03.
    This JRE is installed in my system.
    The error im getting in the browser is
    "THe JAVA RUN TIME ENVIRONMENT CANNOT BE LOADED"

    Well, this needs further investigation, Mr. Watson ;)
    Looking at the output you provided, it seems to me that you ommited the cache_version parameter. (on purpose?)
    The caching process involves the check for newer versions of the jars: this can be done either using the version tag, or letting plugin compare the cached jars with the ones on the server using their timestamp. According to the output you've got, the verification is done using that timestamp. This might be the problem.
    Did you check the logs of your webserver -you're using apache, right? Nothing unusual there? Raised debuglevel there?
    You could try to exclude some possible problems by trying to change the verification process: Instead of using the timestamp, give it a try and use version numbers for your jars.
    Since the version numbers are coded in the object tag in your jsp page, plugin can do the verification without getting the jar-files' timestamps.
    If this solves the problem, the timestamp is definitely the cause of your trouble.
    ;)

Maybe you are looking for