2 replies to this topic

[MikaelH]

Hi
I've converted one application from LV2010-32 bit to 64 bit.
Everything works well, but my LabSQL ADO component is slow.
In my 32-bit LV application a DB-queryl takes 4ms but 1700ms in my 64-bit system, it still works but I can't accept this.
A run both LV32 and LV64 on the same computer next to eash other so it's not a computer issue.

Anybody seen this before?

Cheers,
Mike

[MikaelH]

Hi again
I'm going to give this problem one more push to see if anybody has tried to use the Database ADO Active-X with LV2010SP1-64 bit.
I've attached a VI that explains the problem.

A quick summary:
I’m running LV2010-32 and LV2010-64 at the same time on my W7-64bit computer.
I opening the attach VI in both LV versions.
I have an enum on the FP that executes 3 different queries.
Here is the time statistic for all the 3 queries:

I’ve a disable structure in the code to try two different ways of getting data, both give me the same result.

The problem is that when I'm getting NO data/rows back from the query, it takes LV2010-64bit ages to execute that.
Why?
Is there a ADO-64 bit Active-X Component I should use?
Cheers,
Mike

Attached Files

•  SQL1.vi   33.27K   71 downloads

[MikaelH]

NI has found the problem and filed a CAR for this.
They did give me a workaround, that needs a small change in the LabSQL drivers.
Always before you get the the data, do a PropertyNode: _Recordset.EOF check.

Cheers,
Mike