10-23-2007 11:24 AM
10-25-2007 01:53 PM
Hi womisa,
Could you please provide a longer list of contiguous records, similar to the 3 record list you submitted already? It doesn't look like a rounding error to me-- it looks like DIAdem is loading in the Nth millisecond value for the N+1th datetime value. I seem to remember a similar bug in the ASCII Import Wizard in DIAdem a long time ago. I have already begun pestering R&D about your 2 data base questions but haven't heard back yet. 64 bit integer fields and datetime fields with milliseconds are two use cases that don't come up that often.
Brad Turpin
DIAdem Product Support Engineer
National Instruments
10-29-2007 03:16 AM
10-29-2007 10:51 AM
Hi Achim,
So you're saying the "bigint" import issue and the "DateTime-with-milliseconds" import issue are one and the same? I thought they were separate. Does SQL-Server store a DateTime value as the number of milliseconds since a particular date?
If you want to add any conditions or ordering syntax to the import, you do indeed need to use a VBScript. I am including below a "SQL Wizard" application with which you can do this without needing to program. You will need to edit line 12 in the "SQL Wizard 101.VBS" to add your data base connection string, but otherwise you should just be able to run it. This may not solve your problem, but it should enable you to try out a few things, such as adding an ORDER BY clause, etc.
Brad Turpin
DIAdem Product Support Engineer
National Instruments
10-29-2007 11:56 AM
10-29-2007 12:09 PM
10-30-2007 05:54 AM
10-30-2007 06:05 AM
10-30-2007 06:06 AM
10-30-2007 06:31 AM