Query time for Access DB varies

[Dobbs]

Jay:

1) I looked under the hood of the three native LabVIEW DB Tools functions I'm using (EXE, Fetch and Free Recordset Ref) and none of them use Trim Whitespace as far as I can see.

2) I attempted benchmarking the way I did because it made sense to me.  If it was obviously invalid for getting results, I wouldn't have done it.  Who has time to waste time?  That said, I'm not an expert and maybe you are.  I release the recordset reference after each fetch, but I don't release the connection reference.  The connection reference gets created once at beginning of program and cleared once at end (not shown in the code I provided).  If you contend that releasing the recordset reference would "swamp the query process", then why doesn't it do so on the two laptops, running identical EXEs?

3) Don't know how to check the debugging status of TK VIs.  As I wrote, I'm not an expert.

4) There is no close DB reference in the code I provided, so I can't do what you ask.

[Dobbs]

Santhosh:

Thanks for the advice.

[Eric1977]

---

@Dobbs wrote:

Eric:

I have no problem sharing the project.  Given that I'm not an expert LabVIEW user, I don't know the best way to do this.  I there a tool in LabVIEW that zips up the entire project so you can attach that file to the drag and drop?

---

The easiest way is to put the lvproj file and all the VI's it uses into a ZIP file and attach it in your next post.

[JÞB]

---

@Dobbs wrote:

Jay:

1) I looked under the hood of the three native LabVIEW DB Tools functions I'm using (EXE, Fetch and Free Recordset Ref) and none of them use Trim Whitespace as far as I can see.

2) I attempted benchmarking the way I did because it made sense to me.  If it was obviously invalid for getting results, I wouldn't have done it.  Who has time to waste time?  That said, I'm not an expert and maybe you are.  I release the recordset reference after each fetch, but I don't release the connection reference.  The connection reference gets created once at beginning of program and cleared once at end (not shown in the code I provided).  If you contend that releasing the recordset reference would "swamp the query process", then why doesn't it do so on the two laptops, running identical EXEs?

3) Don't know how to check the debugging status of TK VIs.  As I wrote, I'm not an expert.

4) There is no close DB reference in the code I provided, so I can't do what you ask.

---

What I see from the image in post 5 is an open and close after each Query DB.  

Is that accurately representing what you are challenging for time Benchmarks?

Open and close inside a benchmark loop will be skewed!  Those refnums do need to be released before another reference can be created if the referenced object is not threadsafe. (NOTE: Only one access to any file object can be made at any single time)