communicate lab view with MS access data base

[Elidiane]

I need to read and write dates in MS access through LabView.

I have any vi's about communication labview X access, but when I run the Vi the follow error show:

DDE Open: DMLERR_NO_CONV_ESTABLISHED

What mean this ? How can I solution this problem ?

Thanks!

[Dennis_Knutson]

When you run what VI? DDE is an old and obsolete microsoft technology and there are much better ways to connect to Access or any other database. NI sells the Database Connectivity Toolkit, Mike Porter has posted some VIs here, and there is LabSQL. It's also possible to use Access's ActiveX interface and there have been some examples posted regarding that but I would recomend either of the three previous options before trying that. ActiveX is slower and will be much more limiting. The other options connect to databases with ODBC/ADO which will work with not only Access, but more robust databases such as Oracle, SQL Server, and MySQL.

[Elidiane]

Thanks Dennis for your answer!

haven´t many time that I know labview and I know this technology (DDE) just.

I also know Database Connectivity Toolkit, but my project have a limitation of cost.

I´ll try some technology that you mention.

thanks again.

[andre.buurman@carya]

Sometimes doing things yourself is not the most cost effective way of achieving the end result. Sometimes small investments save loads of time and time is generally more expensive although spend more easily.

[Elidiane]

andre, I absolute agree with you, and I will love if my boss think in this manner, but who give de roles here is him.

I know and my boss know, that time is money, but have more, the client give us a sum of money for us spend in the project, we can´t spend more this, more this result in less profit. This call CAPITALISM!! you know!!!

but return for the question, I have one month to develop anything about communication labview/database, I know that this exist, but I don't know how this work yet.

If you perceive about the subject and can help me, would be much appreciated.

[mikeporter]

Yes, time is money. But time spent troubleshooting a toolkit that you bought is also money. As in many aspects of life there are trade-offs. Buying a toolkit simply means you don't have to pay for the development costs for the toolkit. You still have to pay for the time it takes to figure out how the toolkit works and then pay some more for the time it takes to find problems in it. (Check out the number of post on this forum from folks trying to get the DCT to do something that should be pretty easy...) Plus for something as inherently simple as database access, I think I like knowing how to do it myself.

Mike...