silently open the MS access database

[NewCLAD]

Hello,

I previously worked with labview 7.1 and when I open a MS access database with an automation refnum the MS access was loaded silently, no MS window was launched.

I updated the VI to labVIEW 2012 and now the MS access database launched by labview through automation launches a MS access empty window.

How can I silent the MS access database opening as it is the case in LV7.1 ?

In attached file the VI that opens the MS access database.

Best regards,

Armindo PINTO

[Bob_Schor]

If your old code ran in LabVIEW 7.1, I'm guessing it also used an older version of Office, with older DAO libraries.  Are you using newer Office with newer LabVIEW, or the same Office with newer LabVIEW?

I tried to see what the Options settings were in OpenDataBase, but Microsoft didn't install the appropriate DAO360.chm file (only the .dll, apparently a "known feature/bug").  I was able to find a few things, but I'm not sure it answers your question.

I have had experience using the Report Generation Toolkit with Excel, and can opening it "largely silently" (it will occasionally flash the Workbook when opening), but have less experience linking LabVIEW with Access.

BS

[NewCLAD]

Hello Bob,

thanks for your reply. I use the same Office 2003 version for both LabVIEW7.1 / LabVIEW2012 program. It could be the issue. I need to try out this option.

By the way I solve my problem using the "Hide Window.vi" included in the LabVIEW WIN32 API toolkit.

I will post update on this issue as soon as I install Office 2007 or later.

Best regards,

Armindo PINTO

[Bob_Schor]

It is almost always the case that there are at least 4 ways to solve a programming problem (not counting Read The Manual!).  Congratulations on finding "a solution that works".

BS

[Dennis_Knutson]

I would strongly recommend that you change your entire approach. First, Access is not a database. It is a front end to the Jet database. Using the Access ActiveX is slow and will probably tie you to a specific version of Access the way ms changes the properties and methods so often. Far better to use ADO and SQL commands. You would then be using something much more portable and could easily upgrade to a more robust database such as SQL Server or MySQL.