Suggestion For LabVIEW Experts/NI

[roboticstudent]

Hello,

I am a LabVIEW customer and I use the Database Connectivity Toolset. 

There seems to be many questions on the Database Connectivity Toolset (DCT) and logging/retrieving data using LabVIEW & MS Access.

Suggestion for NI:

Will you please create a video, or a step by step example tutorial for using MS Access  & Database Connectivity Toolset? I looked at the tutorial videos and the only thing you had was on the usefulness of DCT, but not a demonstration on how to use it. Use any example you desire, but have it with Access if possible.

If anyone agrees with the above suggestion, please add your comments.

If anyone else in this forumn is comfortable enough to give a tutorial on DCT and logging/retrieving data using LV & MS Access, you have found a willing pupil.

Thanks.

[Dennis_Knutson]

One of that last posts I saw of yours here where you were having problems said that you had the same path control wired to the open database function and the slope-yintercept subVI (where you write to a spreadsheet file) you wrote. Did you ever fix this? I also asked you to post the actual .udl file and blank database so that someone with the toolkit can actually run your program. The single path wire to different functions is a large mistake and if the write to spreadsheet is working, you clearly have an invalid udl file.

[unclebump]

I have some vi's from several years ago that I can send to you. I wound up moving away from the database setup because of the file size limit. I'm in a training class right now, so it will be a few hours before I can post them.

[tst]

The example finder includes some examples (with Access DBs).

If you search this site for Mike Porter's posts from the recent months, you can find a document with some examples (Access, but pure SQL).

There is at least one 45 minutes web event (video) about using the DB toolkit Here. They may be others.

[rolfk]

Last but not least, MS Access is a nice toy to play with but not a database for any critical real world usage. If you want to store your CD titles in it, or some other private information such a for genealogy, your hobby club belongings or something like that then that is certainly fine.
For an industrial quality application MS Access simply is not up to the task and will cause many troubles in the long run which will cost you a lot more than a full blown SQL server license does. Creating, managing and maintaining databases is a serious business and should be learned that way. The real challange is not how to connect to a database but how to design and set it up.

Rolf Kalbermatter

[Henrik_Volkers]

---

[...]

The real challange is not how to connect to a database but how to design and set it up.

Rolf Kalbermatter

---

an all star answer

[Ray.R]

Henrik & rolfk have summed it up very well.

You will hit a wall faster than a speeding locomotive if you use Access.. The first thing that we found (many years ago already) is that it became progressively slower as additional transactions and / or fields were added!!!

My new contract does include database interaction, using SAP.

The best approach is to design the database upfront... it will save lots of time down the road.

[roboticstudent]

Hello,

Thanks to all for visiting my post and giving useful information.

I understand the challenges to the future of my database if I stick with MS Access, but that is the database I want to use for my data.

Concerning the following post:

______________________________________________________________________________________________________________

One of that last posts I saw of yours here where you were having problems said that you had the same path control wired to the open database function and the slope-yintercept subVI (where you write to a spreadsheet file) you wrote. Did you ever fix this? I also asked you to post the actual .udl file and blank database so that someone with the toolkit can actually run your program. The single path wire to different functions is a large mistake and if the write to spreadsheet is working, you clearly have an invalid udl file.

_______________________________________________________________________________________________________________

I fixed the path control that is wired to the open database function.  Now I can open the dialog box and find the slope and intercept for the data in Notepad. Old friend Trial and Error figured this solution.  

I posted the udl file and blank database and someone looked it over but no one really was able to answer my question.

Which is this:

I can not insert my data into my insert.vi because it wants insert.vi from NI wants it  to be a cluster but  I have array data indicators for my output data in slope/intercept.vi. I tried to convert from array to cluster but it did not work. This is why I am getting so "hummmp" (it makes sense if you see me do it).

Does anyone have a suggestion on how to make my slope/intercept.vi into a cluster that is acceptable to the insert.vi?

[Odd_Modem]

The table has the same structure as the cluster. The first two fields are floats and the last is string. The cluster has to match the table this way in order for the insert to work. When you start to use Access at greater levels of detail you need to pay attention to database issues that are not related to LabVIEW. More help is available with Access help.

[Dennis_Knutson]

Could you point to the post where you posted the udl and the database? A quick sarch of your previous posts did not find any files with a .udl or .mdb extension.