Leaderboard

Just to expand.......... TDMs is a flat-file database. Basically a data table with a look-up table (by name, index etc) with no relationship between entries .MySQL, Postgres, SQLite et. al. are relational databases. A simple way to decide which is preferable for your requirements is to think about what questions you want to ask of the DB. : If you just need to look up data based on a single criteria, e.g. channel names. Then TDMS.. If you need to ask "open" questions such as "How many", "What has" or "When did". Then relational database.

SQLite is a serverless DBMS. You just work with a file directly. It's ridiculously easy. "LabVIEW itself", by which I assume your supervisor means the native APIs, doesn't have a good solution for this. "LabVIEW itself" will in fact make this harder. Your supervisor needs to let you use an appropriate tool for the job.

Yeah, that is definitely a database situation. TDMS is not good for this. Look to the SQLite solution you were given before.

I recommend you check out the appendices in the paper linked in this thread: http://lavag.org/topic/14213-strategy-pattern-example/?hl=%2Bstrategy+%2Bpattern. One way to see the interdependencies is to create an empty project and add, say, a class to it, and see what comes along with it. Look at the tag-alongs and think about whether the linking is logically necessary or not. Paul

If you need to store test specific information (operator, temperature, equipment name & serial number etc... ) with the streaming data, you can write custom properties to the TDMS file. This example from the NI forum works well., just create your own arrays of property names and values to be stored... ( is this the same as the question asked on the NI forums? http://forums.ni.com/t5/LabVIEW/Separating-TDMS-file-data-and-playing-it-back/m-p/2727403#M807331 )

Let's not pollute the labor pool and the community by helping people shoot themselves in the foot.

Correct. Zahrah, I recommend using http://lavag.org/files/file/212-sqlite-labview/ instead.

TDMS is setup for waveform data. For what you are referring to, you need an actual database, not TDMS.

They have identical issues to removing diagrams from VIs. i.e. not cross platform or cross CPU arch.For most developers that create tool-kits, utilities or reusable components that are distributed to other devs; they are not a good choice. If you only have one product and only ever use one OS of a single bitness and that will always be the case then that's fine. - welcome to Labviews version of DLL hell I personally avoid them like the plague-little upside, huge downside. A LLB is superior IMO. However. In your case. I can't help but feel the only reason you are considering them is through desperation - to cure the symptom of a much deeper problem.

Hi guys, thanks for your posts I have added a test build compatible with 2012 here if you are interested