<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: LabView: Good/Bad?? in LabVIEW</title>
    <link>https://ni.lithium.com/t5/LabVIEW/LabView-Good-Bad/m-p/5649#M4331</link>
    <description>I used to use HP VEE. Much trouble and NO support from HP. Anything that&lt;BR /&gt;you have trouble with, they wanted to charge for their assistance. In&lt;BR /&gt;the Window 3.1 version, there were some bugs that they didn't even tell&lt;BR /&gt;their field engineers about, too embarrassed, I guess. We got so fed up&lt;BR /&gt;with them that we switched to LabVIEW and have been very happy. NI&lt;BR /&gt;support is also the best I have ever used, even if it still lacks in&lt;BR /&gt;some areas.&lt;BR /&gt;Go with LabVIEW! You will be glad you did as time goes by.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Jose Miguel Prozzi wrote:&lt;BR /&gt;&lt;BR /&gt;&amp;gt; hi:&lt;BR /&gt;&amp;gt;&lt;BR /&gt;&amp;gt; Why dont you have a look at HP VEE, it is also quite complete.&lt;BR /&gt;&amp;gt; I dont have much experience wiht LAbview.&lt;BR /&gt;&amp;gt;&lt;BR /&gt;&amp;gt; www.tmp.hp&lt;BR /&gt;&amp;gt;&lt;BR /&gt;&amp;gt; jose &lt;BR /&gt;</description>
    <pubDate>Fri, 25 Jun 1999 18:41:56 GMT</pubDate>
    <dc:creator>Craig Dobis</dc:creator>
    <dc:date>1999-06-25T18:41:56Z</dc:date>
    <item>
      <title>LabView: Good/Bad??</title>
      <link>https://ni.lithium.com/t5/LabVIEW/LabView-Good-Bad/m-p/5647#M4329</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I am currently looking for a data acquisition software package,&lt;BR /&gt;and LabView seems to be the best.  Please, share your experience with&lt;BR /&gt;LabView with me, I'd be glad to find out more attractive features and/or&lt;BR /&gt;major glitches.  Also, if you think another package is better than&lt;BR /&gt;LabView, please inform me as well.&lt;BR /&gt;&lt;BR /&gt;Thanx&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Sent via Deja.com http://www.deja.com/&lt;BR /&gt;Share what you know. Learn what you don't. &lt;BR /&gt;</description>
      <pubDate>Wed, 23 Jun 1999 20:11:08 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/LabView-Good-Bad/m-p/5647#M4329</guid>
      <dc:creator>jmliu@iname.com</dc:creator>
      <dc:date>1999-06-23T20:11:08Z</dc:date>
    </item>
    <item>
      <title>Re: LabView: Good/Bad??</title>
      <link>https://ni.lithium.com/t5/LabVIEW/LabView-Good-Bad/m-p/5648#M4330</link>
      <description>hi:&lt;BR /&gt;&lt;BR /&gt;Why dont you have a look at HP VEE, it is also quite complete.&lt;BR /&gt;I dont have much experience wiht LAbview.&lt;BR /&gt;&lt;BR /&gt;www.tmp.hp&lt;BR /&gt;&lt;BR /&gt;jose &lt;BR /&gt;</description>
      <pubDate>Fri, 25 Jun 1999 06:46:56 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/LabView-Good-Bad/m-p/5648#M4330</guid>
      <dc:creator>Jose Miguel Prozzi</dc:creator>
      <dc:date>1999-06-25T06:46:56Z</dc:date>
    </item>
    <item>
      <title>Re: LabView: Good/Bad??</title>
      <link>https://ni.lithium.com/t5/LabVIEW/LabView-Good-Bad/m-p/5649#M4331</link>
      <description>I used to use HP VEE. Much trouble and NO support from HP. Anything that&lt;BR /&gt;you have trouble with, they wanted to charge for their assistance. In&lt;BR /&gt;the Window 3.1 version, there were some bugs that they didn't even tell&lt;BR /&gt;their field engineers about, too embarrassed, I guess. We got so fed up&lt;BR /&gt;with them that we switched to LabVIEW and have been very happy. NI&lt;BR /&gt;support is also the best I have ever used, even if it still lacks in&lt;BR /&gt;some areas.&lt;BR /&gt;Go with LabVIEW! You will be glad you did as time goes by.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Jose Miguel Prozzi wrote:&lt;BR /&gt;&lt;BR /&gt;&amp;gt; hi:&lt;BR /&gt;&amp;gt;&lt;BR /&gt;&amp;gt; Why dont you have a look at HP VEE, it is also quite complete.&lt;BR /&gt;&amp;gt; I dont have much experience wiht LAbview.&lt;BR /&gt;&amp;gt;&lt;BR /&gt;&amp;gt; www.tmp.hp&lt;BR /&gt;&amp;gt;&lt;BR /&gt;&amp;gt; jose &lt;BR /&gt;</description>
      <pubDate>Fri, 25 Jun 1999 18:41:56 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/LabView-Good-Bad/m-p/5649#M4331</guid>
      <dc:creator>Craig Dobis</dc:creator>
      <dc:date>1999-06-25T18:41:56Z</dc:date>
    </item>
    <item>
      <title>Re: LabView: Good/Bad??</title>
      <link>https://ni.lithium.com/t5/LabVIEW/LabView-Good-Bad/m-p/5650#M4332</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I used Turbo Pascal for 5 years to acquire analog signals, read write on serial&lt;BR /&gt;ports, talk to hpib, but it was a nightmare.&lt;BR /&gt;&lt;BR /&gt;We switched to Labview at the ESRF-France, 3 years ago. It took me a 1 week&lt;BR /&gt;labview on site training, plus 1 year of practice to be fluent with Labview. I&lt;BR /&gt;don't regret. Labview is GREAT. It is EASY, It is POWERFUL, totally DEBUGGABLE,&lt;BR /&gt;but is a little SLOW. You must pay attention how you write your code. You can&lt;BR /&gt;do anything with Labview, but you should stick to what it has been designed for&lt;BR /&gt;and speed will not be an issue. I had a college that used HPVEE, but his&lt;BR /&gt;progrms looked really horrible. If you look at HP job posting, They seen to be&lt;BR /&gt;using labview themselves.&lt;BR /&gt;&lt;BR /&gt;Conclusion: Go for Labview !&lt;BR /&gt;&lt;BR /&gt;PS: I am looking for a Labview job in the US. Any ope&lt;BR /&gt;nings are welcome. &lt;BR /&gt;&lt;BR /&gt;Mr. Rollin S. McCarty&lt;BR /&gt;4941 Central Drive,  Apt. 705,&lt;BR /&gt;Stone Mountain, Georgia  30083&lt;BR /&gt;Phone:  770-413-4092 &lt;BR /&gt;E-mail: rolmccarty@aol.com &lt;BR /&gt;</description>
      <pubDate>Sun, 04 Jul 1999 06:10:48 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/LabView-Good-Bad/m-p/5650#M4332</guid>
      <dc:creator>Rollin</dc:creator>
      <dc:date>1999-07-04T06:10:48Z</dc:date>
    </item>
  </channel>
</rss>

