Re: Closing ADODB sub reference outs in VIs? (LV 8.5.1)


"intp56" <x@xxxxxxxx> wrote in message
news:1211895605937-713397@xxxxxxxxxxxxxxxxxx
I download LabSQL, it looks pretty close to what I want.
&nbsp;

I'd suggest to use it, and to send them your additional code in return if
you're alowed to do that... Or suggest what you are missing to the project,
so they can add it in later versions.

I'm looking for a VI that queries a stored procedure to determine what the
parameters are, then creates a LabVIEW cluster with the correct datatypes.
The idea is to call that first to create the Parameters object, then use it
later, particularly for DML operations. (Say insert rows from a LV table.)
I've tried using ADO recordsets to insert large datasets, and found it's
performance to be lacking or unacceptable. I can insert several 1000 records
per second with successive calls to a stored procedure where I specify ahead
of time no result set.

Not sure how ADO does this. I vaguely recall something about it. I think the
values are send item by item, and I think there was a faster way to send the
data by using a variant that directly accepts an array... It's been a while
since I've messed around with that, and I might not have succeeded to get it
working. Googling for "ADO large data sets" or something might give some
clues.

If I really have lots of rows to insert, then I've found it better to
prepare a file, move it to a place where the database can see it, and BULK
INSERT it asynchronously and report the results back later.

Can't imagine that this is the best way to do it, but it's a good
workaround.

BTW, I liked the tip that any reference WIRE needs to be closed, that
gives me a nice rule to know what I need to closed.

But even if there is no wire comming out of a reference property, you still
need to close it. So: every "green" read property should be closed.

Regards,

Wiebe.


.

Relevant Pages

  • RE: Bind ADO recordset from SQL2K query to recordsource for forms datasheet
    ... where the back-end database is a SQL Server database. ... there are limitations when binding forms to the ADO record. ... Forms Based on ADO Recordsets Are Read-Only ... In Access 2002 and later, to bind a Microsoft Access form to a recordset, you must set the Recordset ...
    (microsoft.public.access.formscoding)
  • Re: VB6 Access97
    ... I retrieve and manipulate the data using ADO and all works very well. ... Access has builtin functionality to export data to text files. ... ADO recordsets have a Save method to allow them to be saved to files, ... This email account is my spam trap so I ...
    (microsoft.public.data.ado)
  • Re: Stored procedure executes twice
    ... I have used profiler that is how I discovered it was running twice. ... All access to the DB is through ADO Recordsets ... >> The ADO recordset executes stored procedures. ...
    (microsoft.public.sqlserver.programming)
  • RE: linking to SQL databases
    ... ADO recordsets are incompatible with the Access ... controls and can therefore not be used to populate them. ... They might need to change because the Jet database engine uses a different ...
    (microsoft.public.access.modulesdaovba)