Hello, I am not familiar with the databound grid control you refer to or with databases in general. However, instead of recreating its functionality, you could look into the LabVIEW Database Connectivity Toolkit which simplifies database communication. You can find out more information about this toolkit by going to http://www.ni.com and clicking on "Products and Services." Click on the LabVIEW picture under the Software column. Scroll down to "LabVIEW Add-Ons" and select the "Database Connectivity Toolkit" from the drop-down box. A direct link is <a href="http://sine.ni.com/apps/we/nioc.vp?cid=6429&lang=US";>here</a>.
I did look into using this control. One reference I found (<a href="http://dbforums.com/arch/130/2003/10/358690";>here</a>) says that the DataGrid control has replaced the Databound Grid control. The Microsoft DataGrid control is available as an ActiveX object in LabVIEW. Can you elaborate on not being able to set the record source? I was able to put an ActiveX container on the front panel and insert into it a "Microsoft ADO Data Control." If you right click this object, go to Adodc and then ADODC Properties, a properties window pops up. At the bottom you can set the connection string. There is also a tab at the top labeled "RecordSource." Will this allow you to set the record source to what you require? As for how to bind the ADO data control to the DataGrid control, you will need to know the series of ActiveX commands to do this. Once you know this, you can execute these commands in LabVIEW using the ActiveX palette which is located in the Communication palette. You can also browse the example finder for help in using ActiveX. To open the example finder, go to Help, Find Examples. The ActiveX examples are located under the "Communicating with External Applications" folder. If this does not answer your question, can you post some example code illustrating what you are trying to do or perhaps elaborate more on which parts are causing the problem? Also, I did not understand your comment about running out of screen space. Happy coding, Grant M. National Instruments.
