ShaunR

Do you have the "Database Connectivity Toolkit"? Have you done the following? <h3 id="tocHeadRef">Create a System DSN in Windows</h3> Click Start, point to Control Panel, double-click Administrative Tools, and then double-click Data Sources(ODBC). Click the System DSN tab, and then click Add. Click the database driver that corresponds with the database type to which you are connecting, and then click Finish. Type the data source name. Make sure that you choose a name that you can remember. You will need to use this name later. Click Select. Click the correct database, and then click OK. Click OK, and then click OK. Original Article.

Name: Passa Mak Submitter: ShaunR Submitted: 11 Oct 2009 File Updated: 25 Oct 2009 Category: LabVIEW IDE Version: 2.0.0.0 LabVIEW Version: 2009 License Type: Creative Commons Attribution-Noncommercial-Share Alike 3.0 PassaMak is an API for realising multi-lingual user interfaces in labview. Overview: PassaMak is an alternative to the established methods of creating multi-lingual user interfaces that attempts to simplify both their creation and use. It is a wholely Labview native API (with source) that can scan either a directory of files or vis in memory and create language files that (using the same API) can then be used to translate the user interface at run-time. It is a text file (Excel compatible) translation tool, therefore it doesn't require compiling or special proprietry editors to translate. How It Works: The API can scan a directory (or memory) and extracts the label (tags), captions, tip strips and any ancillary text (such as graph axis, plot names etc) of all controls and indicators on the front panels and any string diagram constants that have their captions (or labels for digrams) visible to a number of language files. These files are in a bar "|" delimited spreadsheet format so they can be sent to translation services where they can easily be edited in a text editor or spreadsheet program. Once the language files have been translated, they can be loaded dynamically at run-time to change all the captions and strings in the application on-the-fly. One, easy to use, vi in your application does all this and supports translations for most complex controls/indicators such as clusters, graphs, booleans, ring controls and many more. Installation. Unzip to a directory of your choice. Do not unzip to the vi.lib directory. Dependencies: Labview 9.0 Find Files (Included) Top Level Vi (Included) Tick Count+ (Included) Cut Array Blanks (Included) LabVIEW Versions: Created with LabVIEW 9.0 Limitations. Unicode not supported. Enumerations not supported. Known Issues: None. License: Distributed under Creative Commons Attribution-Non-Commercial-Share Alike See http://creativecommons.org/ for more information Support: If you have any problems with this code or want to suggest features: please go to www.lavag.org and navigate to the discussion page. Distribution: Full source including examples is available at www.lavag.org Contact: PM ShaunR on www.lava.org Revision History. ----------------------- Version 2.0 Added exectable build example. Added support for Tip Strips. Added support for diagram scanning. Fixed bug #PM-00001 in Top Vi's Path.vi preventing correct identifaction of files when built into executable and no path defined. Version 1.0 Initial Release. Click here to download this file

Hmmm. (Scratches head). What happens if you put the run-time dll in the same directory as your executable? (long shot ).

Try this http://zone.ni.com/devzone/cda/epd/p/id/3491

OK. It probably means you've got a Japanese run-time dll somewhere that is being picked up. Do a search for "LVRT.DLL". There will be a few. Right click on each of them and bring up the properties dialogue. Under details it should tell you the language. Are any of them Japanese?

It is. But it keeps it simple, easy to understand and trivial to migrate to the "proper" way (using stored procs) once a little more experience is gained. PostgreSQL has variable length array datatypes (and then you could use the correct datatype) but MySQL doesn't. These are very, very important considierations.

Try adding the following to your executables "ini" file appFont="Arial" 12 systemFont="Arial" 12

Indeed. But for an introduction to DBs and SQL it will be perfectly adequate and acheive what is required. You gotta open the door before running through it

SQL is all string manipulation e.g INSERT INTO TestDB (Fixture, Employee, Serial) VALUES ('No1', 'Brown','12345'). Will insert a new entry and populate the "fields" Fixture, Employee and Serial number with the values No1, Brown and 12345. (See its not that hard ) For the data, I would use a TEXT field (65,536 chars max should be plenty for most apps) and format my array to colon delimited floating point values. This makes it much easier to get back out and much, much easier to debug. e.g INSERT INTO TestDB (RawData) VALUES ('10.123456,3.1212134,12.11223344') If any calculations are to be made on the data (eg mean values, standard deviation, noise, max-min etc) you can iether post process it in the report query (harder) or save it to the DB as a separate field (easy).

Another little snippet that you may find useful.

I had to make this dicision a while ago...and never looked back. I set up my own "Test" network which I got IT to link to so that anyone with a browser and login on thier network could view test results and other test information. This is still in use and is incredibaly scaleable. I set up an old PC with a webserver using Xampp. Its a fully functioning webserver including Apache, PHP, CGI, SQL,mail SSL and well, everything. But more importantly it is really easy to install and FREE. About 10 minutes and your up and running. Part of the Xampp installation is an SQL server. I set up a set of "Test" databases (we had 3 product lines at the time so I decided to have a different one for each...personal choice to partition the data better. You could have one or you could have one for each station..its up to you how you set it up). The test stations (18 of them, 6 per line) all pushed thier test data into the various databases using the Labview SQL toolkit. I just made a drop in module for the existing test stations so that instead of writing the results to a file, they wrote it to the database. I then wrote a few webpages (started as two, is now about 80 and quite sophisticated with graphs, process capabilities, searchable queries etc) that queried the databases so that any user could view the results in a web browser. The thing about this setup was that it operated perfectly fine on its own as a standalone system, but once it was up and running, IT really took an interest (especially after the big guns wanted to see the pretty graphs on their laptops in the office ) and they have now taken the responsibility of managing and updating the webserver. From my point of view (and ITs) it creates a defineable partition between the test network and thiers and it is a technology they understand. The big guns loved it because there was no captital cost (well, apart from the SQL) although I did persuade them that they should make a donation.

Still reeling from that one eh?

1. Read from spreadsheet file. 2. Delete array element. 3. Write To Spreadsheet file. Either way its only a 30 second vi. How easy do you want it?

Even Excel cannot save its own page breaks to a text file.

Ummm. VI, TCPIP, UDP. IMAQ, Bluetooth, IRDA?

As Asbo said. You have to select a scale that shows the minor markers.

I think I see. Like this?

Sorry. Here it is in a version you can open.

Here you go

Its what I expect since I think of refs similarly to pointers. An unitialised pointer is a "null" pointer (no memory allocated). But I think Daklu thinks of them as references to objects and that by placing it on the diagram the "pointer" is allocated. So I got the impression (rightly or wrongly) that he expects a reference to an uninitialised ref to be the same as an initialised one since it is the same object. In that respect. Daklus last image seems prefectly normal to me, however it is an "unexpected" result.

I'm not sure its is that smart. It basically just typecasts the ref to a U32 (or maybe an I32) and compares the values. It does the same for VISA and IMAQ sessions. If you think about your uninitilaised references, the value when typecast is 0 which is not equal to its value if its initilaised.

Its more of a reboot than a reset. The state depends on what you have set the power-up states to be from MAX and the position of the DIP switches (refer to the manual)

Told you I get confused as to which propery nodes need closing of the refs

Sweet

You can't help but laugh AT them in this