Off-hand, I see things from the picture that might cause problems. The error cluster wire is supposed to pass through a shift register. In a for loop situation you must do this to allow the first error to shunt the rest of the loop iterations when there is an error.
Thanks. The shift register suggestion worked. Great explanation--- very direct
Second, the loop counter might possibly be the primary key of the table (the ID field). If you are writing to the same table over distinct executions of the vi, then you will be attempting to use the same primary key for a different row, and this will generate an error because primary key values have to be unique. You need to query the database to find the maximum value of the primary key and start your logging after that, or log to a new table.
How do I log to a new table? Also how does one go about querying the database to find the maximum value of the primary key
Three, there are a certain mumber of broken wires that need to be fixed. The error cluster broken wire would be fixed by using a shift register.
Now solved
The connection reference is passed out of the for loop with auto-index enabled (the default for the for loop). You may right click on the output tunnel and turn off auto-indexing in order to get a scaler.
That is a solution that will work for newer versions of LabVIEW, but for older versions, if the loop never runs because "numeric" is zero, the connection reference will not be valid and you will not be able to close the database. It would be better to pass the connection reference around the loop, to the close vi, and allow the dataflow to mediate execution with the error cluster wire (this is the normal LabVIEW idiom). finally, the boolean array seems to be a problem that you will have to sort out. If it is in fact accidentally an indicator rather than a control then its dimension will control the number of iterations of the loop, unless "numeric" is less than 'array" dimension, in which case 'numeric will. This could be an additional "got ya" once you get it to talk to Access.
Can you attach an example of what you mean using what I have already if possible.
Just from looking at the picture, where I assume that the cluster bundle is representative of the table row, what is a string array doing in there? What SQL datatype does that map to?
Cluster bundle is representative of the table column. The string array was meant to reflect the presence of the tables. I really wanted to have the array reflect the current slope and y-interecept from my subvi from the table. Everytime new data is entered for one axis, one would get a new slope and y-intercept to replace the older calibration. The new information would then automatically enter the table.
