I don't know about that. My profile says I have 505 (before this post) and my avatar says 509. Both are above the 500 posts implied in "The 500 club". I wonder what I have to do to get into the club.
This exercise gave me the opportunity to find this TestStand patch that fixed TestStand crashing whenever I tried to use my new VI. I probably ignored a message about it during installation.
Here are two ADO DB toolkits that might give you a place to start.
http://www.ib-berger...tion=adotool_en (this links to MS' ADO Programmer's Guide http://msdn.microsoft.com/en-us/library/ms807642)
http://jeffreytravis...ost/labsql.html (this one appears to be older)
Jim
I have a "sandbox" sequence that I use to test my products and develop new tests; it contains all of the sequences that I use for production as well as utility sequences and whatever is in development. I currently use it by skipping every step except the ones I'm working on, but I'd like to generate a list of steps at the beginning of the execution that will allow me to select which steps to run. I figure on making a boolean array and using Preconditions to decide whether or not to run a step. I've written something similar, but it depends on a static list of steps. I want something to dynamically adapt to the ever-changing sandbox sequence.
How can I get a list of steps from a VI called at the beginning of the sequence? I've looked at the OI examples and nothing jumps out at me.
Thanks
It's been a long time since I worked with this, and I didn't have the correct hardware then so I don't have experience with it, but I remember something about some NI hardware being able do do something like this. How's that for concrete help?
The feature of the hardware is called Digital Change Detection, and it eliminates the need to poll your input lines and this KB sounds like what I vaguely remember.
It might be worth considering the schema TestStand uses. It may be a dangerous guess, but I'm guessing that they've put a fair amount of though into normalizing test data. It looks sound to me.
That sounds like you would charge more. Not as a penalty for foul-smelling code, but because you're being realistic in that you'd have to include the learning curve or the time to rewrite it.
My take on the question was that Ben was asking was whether it would be ethical to charge above your standard rate to extend a particularly odoriferous project (after accounting for the things you mentioned) simply because the work involved is so distasteful?
Yes, unless it's your [company's] code!
I don't think the reason for charging a premium, or even that a premium is involved, is important. It might, however, come up in the discussion after the customer receives your quote.
As far as the problem in your original VI, you're using Shift Registers with the Match Regular Expression node incorrectly. You can't use the Offset After Match if you're only going to search what was found before and after the previous match. Savvy?
Yours will not miss nested tags line break characters. If the tag spans multiple lines the "bad" regular expression will fail.