I had a similar problem with the SQL Toolkit. Retrieving a record took a
horribly long time and there was a lot of hard disk access. The problem
turned out that I had turned logging (or tracing) on in the ODBC setup. You
can turn it off (this is for access) by opening data sources (ODBC),
selecting your data source and going to the tracing tab. Choose stop tracing
if it is available.
I find the complete SQL session is fast enough. It will get a single record
with 151 fields in a second or two from Oracle over the company network. It
seems to be slightly faster using a local access 97 database.
It is somewhat slower on older machines. I usually use a pentium III 450. On
a pentuium 133 it is very slow. I use windows 2000, and LV6.01 on the
development system. The execu
table runs under win NT4 and 95.
wrote in message news:94l2ub$onb$1@nnrp1.deja.com...
> I have win2000 machine, LV 6, LV SQL Toolkit installed on my machine.
> Everything was worked fine until i started noticing that my SQL VIs
> take 7-10 seconds to connect to DSN. During this time i hear crunching
> sound of my hard disk. Execute SQL.vi also takes longer time. I have
> another machine with same OS and LV and that runs normal and much
> faster than this one.
>
> The only thing i could relate this to is that i installed LV5.1 after
> LV 6.0 and in the registry the current version is LV 5.1. But i'm not
> sure if thats whats causing the problem. This behaviour is independent
> of the database i'm connecting to (whether its local or over the
> network). I was wondering if any of you G guys have seen something like
> this and would relate to something? Do i need to install LV 6 again. I
> know that the problem is not in LV and neither in SQL toolkit. Its
> somehow
either related to ODBC Administrator or the registry. comment??
>
> Thanks a bundle to all of you.
>
> regards,
>
> Paracha
>
>
> Sent via Deja.com
> http://www.deja.com/