DATABASE TOOLKIT unable to run

[aveamon]

Hi, im already using lv 2016(32b) with db toolkit v.16 installed. I cant even run a vi because of many subvi's errors inside every db toolkit vi. I have no idea whats going on. 

Windows 10 64b

i installed odbc data sources(both 64 and 32bit) and created a .udl file with it. 

errors i've got are below.

[Yamaeda]

You must send the .udl path as a Path, not a String. If you send a String it must be the Connection string (which is actually written inside the UDL if you want to extract it).

/Y

[aveamon]

Big thanks for reply!

Nothing changes, i think there is a major problem with ADODB

but how to solve it ;/

[Yamaeda]

Hmm, yes that could be problematic. Reinstall DB Tool, (re)install correct .NET versions, then we might have to relink to the correct .NET class is it has lost the linkage somehow. 😕

/Y

[aveamon]

i reinstalled this again, no result. these below are my versions of .NET, looks fine;/ i also tried to install db tool v.15 but it seems like i cant do it on lv 16;/

is there any other mechanism that will allow me to put some records into the mysql table(with connection lost terminal)?
maybie there is a problem with this(2nd screen)

should i configure this somehow?
again, thanks for responce!:) i belive we can make it work 😉

another think is, i just want to run the connection for now, maybie i should build some kind of proper function instead of this what i have now, on screen no.9?

i created .udl file using this functionality on screen no.10

[aputman · Accepted solution]

I assume your program is written for FPGA because i can see references to it in your pictures.  I know nothing about FPGA so my response may be way off base.  The error says that the wire type is not supported in the current target.  This makes me think that you can't use the database toolkit on FPGA. 

[aveamon]

Thank you for response,

this program is out of fpga so it has nothing to this;/ 

[aveamon]

I think there is a problem with .net, seems like ADODB is missing, any ideas how to fix that?

[aveamon]

U were right! this wasnt fpga vi but it was on the controller! as in the picture below 

[aputman]

Well....I saw that in your picture but since I am not familiar with FPGA, I didn't question.  Glad that you got it working.