How to solve Labview 2016 (32bit) database error on Windows 10.

[Justin2007]

Hello,

I have a labview database read/write software (32bit), which works fine on windows xp /2000 / 7 (64bit). But it does not stable on windows 10 (64bit) at all.  It pops up an error on most of the time. Please see the attached  database VI. After starting my software, usually, there is no error on reading the frist database. but it pops up an error when opening the section database. the error code is -2147418113. it seems like it will be more stable if I put more than couple seconds delay before opening the second database.

Could anyone help me to figure out how to solve this issue?  Appreciate.

Steven

[Bob_Schor]

Justin,

     Instead of attaching a picture of the Block Diagram, which we can only "look at" (unless you want us, ourselves, to take the time to try to recreate it from the picture), attach the actual VI, which lets us really examine it closely, and even try to execute it.  Note we can learn "non-obvious" things, like whether you are using 32-bit or 64-bit LabVIEW, what version, etc.

Bob Schor

[Justin2007]

Thanks for your reply. See the attached VI.

[Bob_Schor]

Thanks, Justin.  Now that I see the code, I can at least ask "better questions" ...

• I looked up the Error you reported (do you know how to do that?).  Its description was something I'd not seen before -- "LabVIEW:  (Hex 0x8000FFFF) Catastrophic failure".  But before we panic and call NI, a few more questions ...
• You say "Usually there is no error on reading the frist (first?) database, but it pops up an error open opening the section (second?) database".  First question -- did you mean "first" and "second"?  It looks like the code only does one database -- do you mean that you run the code, it stops, then you run it again?  What are the inputs when you run it?  Are they the same both times?
• Do you know precisely where the error occurs?  For something this small (though you do have a For loop, and that may take a while), you can open the Block Diagram, turn on "Highlight Execution" (click the little light bulb, the fifth icon on the toolbar), and run with the Block Diagram visible to spot when the Error occurs.
• Why do you have a 200ms Wait before the program exits?

[Admission -- while I've done a lot of things using LabVIEW, including linking with Excel, I've never used its DataBase tools, so I may miss some subtle details that, I hope, my colleagues can spot ...]

Bob Schor

P.S. -- do we call you Justin or Steven?

[Justin2007]

I don't know what the code 0x8000FFFF mean.

my software needs to open multiple tables from 3 Access databases. This VI is a sub-VI to read a table from a database. I assign a different password, DNS name and table name on this sub-VI to open the file that I need. the first database and the second database are two different database that the software read in order.

when the error occurs, it happens on the first step of this sub-VI. The DB tool Open Connec (String) VI creates an error.

200ms is the time, that I want to ensure there are at least 200ms break before this function is called again. I found out the longer time, the more stable, right now I put about 5 seconds delay in there. but It still pups up an error 3 out of 10. The executable program is installed on a windows 10 compact computer. Is that because the computer is not powerful enough?

[natasftw]

What version of access do you have on the various PCs?  Is it the same across each?

[Justin2007]

All the databases are the same version, that are .mdb files, should be access 2003 database.

[Justin2007]

I guess the Labview does not close the thread right away after a database operation is completed. It takes couple seconds to close it. Could anyone please give me some suggestion? 

[Bob_Schor]

I'm not sure how LabVIEW is interacting with Microsoft Office routines, but I've seen similar issues when using the Report Generation Toolkit to work with Excel Workbooks.  When I tried to do a "Create or Modify Workbook, Close Workbook, Reopen Workbook" sequence, I used to get a "mysterious Error" that seemed to be Excel-related -- putting a few hundred millisecond delay between the Dispose Report and New Report seemed to fix it.  Sounds like you are experiencing a "Variation on a Theme by Microsoft" ...

Bob Schor

[Justin2007]

The software works on Windows7 64bit and windows xp. I add 10 seconds delay on the windows 10 computer, it still pops up an error. I really have no idea how to fix it. I am waiting for a solution. any help will be appreciated.