i2dx

to be honest, this discussion makes me bash my head against the wall: for a little more explanation: I'm active in bulletin boards since almost 12 years and almost every year someone in whichever forum is crying for moderation, because he/she feels embarrassed by NULL-posts. I have heard the arguments again and again and I know the result of such discussions: nothing will happen. First, because obviously nobody wants to be the censor, who has to read each post carefully and check whether it may please a Premium Member or not - <ironic> or may be suitable for normal members but not for Premium Members ... </ironic> Second, because nobody in an internet forum really wants censorship. I am glad, that spam is removed, and that's enough. Come on guys! We are big boys, use real expensive toys, are responsible for 100.000$ ++ testing systems therefore we should have the balls to withstand a few NULL posts and finally should be able to make usage of the ignore button - it's easy (trust me ) I've done this with alfa before and it works!

QUOTE(Sally @ Apr 21 2007, 10:12 AM) I am not sure, if I understand your question right, but *in my world* you don't need a back button, because, this functionality is availiable allmost automatically: If you have set the SubVI behaviour in your main VI with "open when called", just check the "Close, if originally closed" checkbox, too and you'll get back to the Main VI, after your SubVI has finished. If you have set the VI appearance in the VI Properties Dialog to "Dialog", the called VI closes, after it has finished. If you are using VI Server and call your *SubVIs* dynamically, want them to stay open, but bring the MainVI Window to front, you could use the "frontmost" property ...

thanks for the link

you can use this VI http://forums.lavag.org/index.php?act=attach&type=post&id=5445 to count each call of a VI ... or you can take a look at toos->advanced->VI metrics

QUOTE(Tomi Maila @ Apr 8 2007, 07:54 PM) ah, you just wanted to plug your blog? <SCNR>

I would not see any problem with this. LabVIEW is a hightech product, and mankind needs hightech products to master the coming challenges (global warming, etc) without a dramatic decrease in life standard. Whithout hightech we will soon have to grow our own potatoes in our garden again (what will probably be a problem in the 71. floor in NCY ... ), and that will be much more uncomfortable than working in an air-conditioned office, staring on a computer display, the whole day - so nobody wants that. Even though I don't like to sound like an NI Sales Engineer: LabVIEW is deeply enrooted in many different industries, even so if *interest* on google decreases, it's no indicator for me that the interest in LabVIEW itself decreases. Google does not know everything - at least I hope so Even against *this trend* I'd like to predict a bright future for all engineers, who have knowhow in technology and software.

QUOTE(TiT @ Mar 27 2007, 09:37 AM) I have no knowledge about LabSQL, but the increase of memory of exactly 4 bytes each write operation leads me to the conclusion, that you have an issue with an open reference. I don't know where to search, but I'd search for a reference, which is not closed.

QUOTE(Mike Ashe @ Mar 26 2007, 06:53 AM) yes, I have tried. You can install LV on this *machine*. The performance is slow, but acceptabe for the mentioned purposes, and of course the speed depends on the ammound of memory, the VPC gets ... I don't know if cou can run a VPC inside a VPC, but I guess, no ...

Hi folks, this is somewhat off topic here, but I think it might be usefull: Microsoft is providing a free copy of Virtual PC 2007 and a VPC image with a fully licensed Windows XP Pro. Virtual PC emulates a PC on your machine and this comes really handy, if you have to test installers, exes, and so on ... You can download the VPC-Image here: http://www.microsoft.com/downloads/details...;displaylang=en and the Virtual PC 2007 package here. It might be usefull for testing Beta-Versions ... and so on, and so on. Don't miss it!

QUOTE(karellen @ Mar 24 2007, 11:56 PM) If the vendor does not provide a LabVIEW driver, I guess, you'll have to write your own. Get a copy of the documentation and use the LabVIEW TCP/IP VIs to establish a communication ...

QUOTE(Sally @ Mar 24 2007, 03:50 PM) YES QUOTE(Sally @ Mar 24 2007, 03:50 PM) can graph saved at data base?? that depends on the database and how you want to save the grap data

QUOTE(Val Brown @ Mar 24 2007, 02:19 AM) no, 1.6.3 is the current version for LV 8.2 You can get the newest version by clicking at the link in my signature ... now I have an english information and download page, too (BTW: if someone of the native speakers finds errors in the text, please let me know - and I am searching for a volunteer to correct the manual [yes, I really have startet and I am on page 10 ]) If you want to stay informed, you can register at my forum (the link is on the download page) and subscribe to the pinned topic in the http://forum.ib-berger.com/index.php?showforum=12' target="_blank">ADO-Toolkit forum. I'll announce all new versions in this thread, so you'll get an email automatically, if there are news regarding the ADO-Toolkit.

ok, I just tried it out, and I can not find a memory leak: I have used this vi: http://forums.lavag.org/index.php?act=attach&type=post&id=5267 on LV 8.2, with ADO-Tool 1.6.3 for LV 8.2 Memory usage before the start: http://forums.lavag.org/index.php?act=attach&type=post&id=5268 Menory usage while running: http://forums.lavag.org/index.php?act=attach&type=post&id=5269 Memory usage the VI finished: http://forums.lavag.org/index.php?act=attach&type=post&id=5270 I have inserted 5000 rows at 20 Hz and there was no significant increase of the used memory during the VIs run. This is the table, I inserted in: QUOTE Can you please use the attached VI, run this test on your machine and tell me the results? Maybe you have noticed the "sawtooth" in the CPU usage. The increase of the CPU-load occurs, when a memory block is freed ...

QUOTE(alukindo @ Mar 23 2007, 04:51 AM) ok, that's really strange. I have an application (written with ADO Toolkit 1.5.x and LV 7.1.1) running at my customer, which is a "DB Proxy" where up to 30 Clients connect via TCP/IP and send up to 60 (peak) SQL-Queries (SELECT, INSERT, UPDATE) per cecond. I have implementet all Queries as Stored Procedures on the MS SQL Server and I did not experience a memory leak. The DB connection is open from "Server Start" till "Server Shutdown" ... Which LV Version are you using, and which Version of the ADO-Toolkit? Please make sure, that you are using the latest version, because I will only debug (of course) the latest one

QUOTE(alukindo @ Mar 22 2007, 08:58 PM) hmm, it's the first time someone is reporting a memory leak, I never got bug reports in this direction before. I'll start a search at the MSDN, maybe there is a known issue with ADO and SQL Server, but it may take a while. Therefore I have no solution at the moment. Maybe you can check, if you have installed the latest version of MDAC? MDAC 2.8 is the current version, and if we are lucky, this issue is allready solved

QUOTE(ControlEngineer @ Mar 15 2007, 09:44 PM) I'd try subpanels Help->Find Examples -> Building User Interfaces -> General -> Simple SubPanel ...

QUOTE(Mike Ashe @ Mar 12 2007, 08:48 PM) thanks yes, I think the CC is the right license, because most users do not want to be forced to publish their code as Open Source and I don't want to force anyone to use a specific license.

just to emphasize the iHype http://www.heise.de/ct/schlagseite/07/06/ just click on the small picture to enlarge it, here is the translation: "The iPod has revolutionized the way we are listening to music. The iPhone has revolutionized our mobile communications.This device revolutionizes our personality. The iPrompter tells us always what we have to say"

QUOTE(didierj @ Mar 7 2007, 11:09 AM) I whish you the best, too and I wish you good lock in your new job! Hope to see you from time to time in the lounge! QUOTE(tcplomp @ Mar 7 2007, 01:51 PM) And yes you can do LabVIEW at 300 km/h in a high-speed train or a 120 km/h normal train. ACK, I did a lot of LV coding at 300 km/h (in the InterCity Express ...)

... or you can use LabSQL or my ADO-Toolkit for LabVIEW

QUOTE(Aristos Queue @ Mar 1 2007, 11:28 PM) oh, please don't take that to serious. I think it's beta, not because it's unstable or buggy, like a *real* beta version, I think it's *public beta* because it's a brand new feature, which is not jet *finished* will develop through the next releases of LV. You can compare that in a way to trees in LV 7.0 or the Event Structure in 6.1, which had a very basic functionality in the first release but grew up to a realy importen aspect in LV. For me this is like an invitation: "hey guys, we've got something new, please check it out, we'll collect your feedback and make the best out of it". So I try to get used to it, think about the possibilities and try to imagine where to use that technique in my next project. Can you live with that?

hmm ... I just took a look - it is a lot of work to translate them all ... puhhh ... and I am affraid, I don't have the time ... and on the other hand - I am used to the englisch version

Guy's, I'd really like to thank you! The ADO-Toolkit Downloads reached a new maximum in February: 471 DOWNLOADS in one month! I'm glad that you like my tool - this is a great encouragement to keep on developing and improving!

QUOTE(Tomi Maila @ Mar 1 2007, 05:14 PM) Bugs in LVOOP? LVOOP is a public beta ...

QUOTE(orko @ Mar 1 2007, 12:10 AM) Why use 8.0.1 if you have 8.2? I was really disapointed about the quality of 8.0 and did never use it. But I am happy with 8.2 (as you can see in the "things that have improved thread"). I still use 7.1, because I have a large project in 7.1.1 which is *finished* but sill maintained, and I don't want to spend extra time with upgrading ... QUOTE(Aristos Queue @ Mar 1 2007, 06:44 AM) Use 8.2. And please forgive us for 8.0. Every software team has bad days. We tried to pack ours all together in a couple months so that we wouldn't have any more bad days for the next several releases. ;-) I forgive you And I still believe - 8.0 was a marketing driven release (or, the SEs/AEs/FEs, I know personally got really nervous, because they had no new release to announce one year after 7.1 ...).