asbo

What is "kS"? I know "ks" as kilosecond but can't come up with a unit for "S".

This is pretty basic, but since you didn't mention it specifically: are you using the exact same runtime version? Are they all using the same OS patches? Are they all even the same OS, for that matter? Do they all have the same resident processes? Logged in with the same user privileges?

It's certainly not something I'd put down as obvious, and I don't any mention of the function in the help file (LV2009), so, yeah, it'd be a good nugget. It would almost be better if a checkbox hid its label by default and only showed the boolean text when dropped.

Woohoo! Feel free to kudo

Try cmd /c ""C:\Program Files\OpenOffice.org 3\program\scalc.exe" "macro:///IES13148.Module1.PrintDocument(C:\Documents and Settings\test13.csv)"". My initial test was cmd /c ""c:\foo bar\hello.bat" bar baz" where hello.bat is simply @echo %1 and bar and baz are separate parameters. You can stick them together by putting them in quotes ("bar baz") but then the quotes are included in the output. You can nest quotes within those quotes without consequence ("foo "bar" baz") and the output is literal, even with a pair of double-quotes. You can actually drop the trailing quote for any of these parameters and it'll drop it in the output, but that's kind of taking advantage of the parser and you can't guarantee a particular outcome anymore. The ^ character is the escape character, but I couldn't get it to make any difference. This is all assuming your space in the path is going to mess things up, and that you'll need to encapsulate it in quotes, of course. There's an off-chance that OpenOffice would accept single quotes instead of double quotes to preserve the macro's parameter. Cop-out: is there any reason you can't use 8.3 filenames here?

What about cmd /c "C:\Program Files\OpenOffice.org 3\program\scalc.exe" macro:///IES13148.Module1.PrintDocument("C:\Documents and Settings\test13.csv")?

I thought I'd throw out there that the key bit here is the breakpoint - otherwise, all you've done is dropped a probe on a VI which is instantiated multiple times in parallel, and LabVIEW doesn't have a way of knowing which instance you want to look at. By placing the breakpoint, a specific instance can be brought to attention, at which point the probe you dropped is tied to that instance.

You've forgotten - that moment of disillusioned victory.

Don't overlook the possibility that it being implemented is what we see as the bug.

It'll be a sad joke, but a wonderful dream ...

Actually, we're talking about that very package over here, which offers a little bit more insight on it.

Thanks for the benchmark. Do you have any direction on where optimizations can start? I've not worked directly with the mySQL protocol before, but I suppose reading through some of that would give me some insight. I presume the "Row" case of the _return_packet VI is where you could use some pre-allocation. Maybe if I get some free time tonight I'll start playing with this.

What quantifies large or small recordsets?

Ahh - that's what it's called! I knew LV used something other than division for the node. Yes, that's the one

You could divide the number by 100 and use the quotient (integer result) of the operation.

Very cool. Thanks! Edit: Props go to hooovahh for this link, it messes with a few other things related to the console window.

Awesome! Do you have any code that will create a console window for output if there isn't a parent? Certainly would be handy for development.

LV8.6 is asking for a control typdef, Joystick.lvlib:ButtonState.ctl. I don't know if a license prohibits you from posting that here, though.

Are you passing relative paths? Referencing the help file on SCC/LVMerge I made that mistake at first as well (I was getting error code 7 out of NI_FileType.lvlib:Get File Type.vi). Using absolute paths worked fine, though. C:\Program Files\National Instruments\Shared\LabVIEW Merge>LVMerge.exe "C:\Program Files\National Instruments\Shared\LabVIEW Merge\base.vi" "C:\Program Files\National Instruments\Shared\LabVIEW Merge\theirs.vi" "C:\Program Files\National Instruments\Shared\LabVIEW Merge\mine.vi" "C:\Program Files\National Instruments\Shared\LabVIEW Merge\output.vi"

Is there any reason you can't call the LV app using something like "start /wait $exe"? start is a Windows-specific utility, but I'm sure other platforms (if you need them) have something similar.

It looks like you're heading in the right direction - still no luck in setting up LVMerge properly?

I had to go double check the Options panel to make sure I was thinking of 'tread' in the right way.

I don't see it anywhere either, but I'm not surprised - when exploits are found for a particular version of a web application it's easy to get burned listing the version somewhere. Whoo, google!

Since it's probably not just a single VI, it's best to package everything into a ZIP file and then attach it to your post.

I didn't know about this!