Jump to content

kosist90

Members
  • Posts

    16
  • Joined

  • Last visited

Profile Information

  • Gender
    Male

Contact Methods

LabVIEW Information

  • Version
    LabVIEW 2015
  • Since
    2012

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

kosist90's Achievements

Newbie

Newbie (1/14)

  • Week One Done Rare
  • One Month Later Rare
  • One Year In Rare

Recent Badges

1

Reputation

  1. Better approach would be not to hide credentials from a user, but to create such user at MySQL server which will have limited rights. And then, even if user will know his credentials - then he can't make any harm to server due to limited access rights. Do you create connection via popup window of Data Link all the time when application is used? If so, then you don't have to - it is enough to create it once, and store to file. Will users have access to source code? If yes, then create VI which will connect to server, and have credentials stored inside. Then, the easiest way will be to password-protect such VI (but be aware that password-protected VIs could be easily opened anywayt), or could be built into PPL - so user can not access its block diagram. But PPLs have its own constraints. If users will use application as exe, then store connection string directly in the application - so users even will not know that there is used some Data Link for that.
  2. I've tested it just now, using latest VIPM 2020. After VIPM is installed, TCP/IP checkbox is not set for LabVIEW. And, when trying to install some toolkit the following error is shown: But, when I've opened Settings -> LabVIEW tab -> pressedVerify (connection) button, then VIPM restarted LabVIEW, set TCP/IP checkbox, and was able to successfully connect to LabVIEW. Such trick could be done by Post-Install Action (for example, if it is VIPM package). LabVIEW installers also support option "run executable at end of installation", so I guess other kinds of installers could support similar post-install actions.
  3. Dear Community, let me present our new ANV Database Toolkit, which has been recently released at vipm.io. Short introduction to the toolkit is posted by this link, and it also describes steps which should be done in order to use this toolkit. ANV Database Toolkit helps developers design LabVIEW API for querying various databases (MS SQL, MySQL, SQLite, Access). It allows to create VIs which can be used as API with the help of graphical user interface. When using these VIs, toolkit handles connection with the database, thus relieving developers of this burden in their applications. It has the following features: Simplifies handling of databases in LabVIEW projects Allows to graphically create API VIs for Databases Supports Read, Write, Update and Delete queries Supports various database types (MS SQL, MySQL, SQLite, Access) Overall idea is that developer could create set of high-level API VIs for queries using graphical user interface, without actual writing of SQL queries. Those API VIs are used in the application, and handle database communication in the background. Moreover, SQL query could be applied to any of the supported database types, it is a matter of database type selection. Change of target database does not require changes in API VI which executes the query. After installation of the toolkit, sample project is available, which shows possibilities of the toolkit in terms of execution different types of queries. Note, that in order to install the toolkit, VI Package Manager must be launched with Administrator privileges. This toolkit is paid, and price is disclosed based on price quotation. But anyway, there are 30 days of trial period during which you could tryout the toolkit, and decide whether it is helpful (and hope that it will be) for your needs. In case of any feedback, ideas or issues please do not hesitate to contact me directly here, or at vipm.io, or at e-mail info@anv-tech.com.
  4. Yes, I was using it and it works fine; I guess no fixes are needed. It is possible to supply there cluster type, and read it back - so if you could publish it, that would be great. Thank you very much!
  5. @drjdpowell, let me ask whether do you plan to release this version as the new release?
  6. Dear all, I was asking this question also on NI forum, but didn't get answer yet (https://forums.ni.com/t5/LabVIEW/Create-custom-quot-Method-override-quot-window/m-p/4075683). Let me ask the same question here. Is there a way to customize "Method override" window, to include there some more features (like proposed here , for example)? I was checking this library (C:\Program Files (x86)\National Instruments\LabVIEW 2020\resource\Framework\Providers\LVClassLibrary\NewAccessors\MemberVICreation.lvlib) and found method CLSUIP_CreateOverride.vi (C:\Program Files (x86)\National Instruments\LabVIEW 2020\resource\Framework\Providers\LVClassLibrary\NewAccessors\CLSUIP_CreateOverride.vi). But it seems, that this is not the one which calls dialog window. I do not want to change override logic, just would like to add more features to window which allows to select the VI to override. So I'm curious, whether this is possible - or better would be to implement custom Project Provider for that... Thanks a lot in advance!
  7. Thanks a lot! We're going to try it, but it seems that this is what we need, thank you! Upd: I've installed and tested it. It works fine, thank you - data is converted to array of clusters, so now it is possible to read all table's rows and convert it to array of clusters.
  8. Actually, we have implemented it in the following way - I attach snippet, and VI itself. VI is broken, b/c it is not part of the library... And the issue is that we are kind of able to use this solution, but then we need to manage somehow the fact, that it should be part of SQLite library. And then, we will not be able to update it from VIPM, b/c we will loose the changes. Could you please suggest, whether such solution could be the part of the original toolkit? If so, my colleague could open pull request, or something... The original VI (which returns just single cluster) was modified in a way, that now multiple rows are read, and built into array. And then, this array is possible to convert to array of clusters using "Variant to Data". Execute SQL (Array Variant Cluster results mod).vi
  9. Thank you for the answer! Actually, I'd like to prepare some "universal" VI, which could be reused to read different cluster types, for different tables. My colleague has implemented code which does something similar as reading of variant is done (Execute Query polymorphic VI), but anyway it has limitation of column numbers, and it uses some Vis from your toolkit which have "private" scope. So actually then we can not distribute it, because it is not part of toolkit's package... As we use LabVIEW 2015, VIM is also not a solution for us... The only workaround now seems to be to convert 2D strings array to cluster somehow - but that is also not the best solution...
  10. Is there a way to read from database array of clusters? It is possible to read single row as cluster, but I'm curious whether it is possible to read all rows to clusters array?.. Thanks a lot in advance!
  11. Thanks a lot! Now I see - I didn't know, that there is no exact standart for it.
  12. Let me, please, also ask a question regarding the toolkit. Currently to prettify JSON string, I use function Reformat.vi. But, no matter which value of "Pretty Print Levels" I set, the output is the following: { "Item":{ "Property1":{"Name":"Property1 Name","Active":true}, "Property2":{"Name":"Property2 Name","Active":true}, "UID":43, "Active":true } } But, I'd like to have it as the following (with prettified nested objects): { "Item": { "Property1": { "Name": "Property1 Name", "Active": true }, "Property2": { "Name": "Property2 Name", "Active": true }, "UID": 43, "Active": true } } Is it the expactable behavior, or some kind of bug - that somehow it does not prettify nested JSON objects... JSON itself I generate using Unflatten JSONpath Array to Object.vi function - as inputs I set JSON paths, and values - and after that, Reformat.vi is applied... Thanks a lot in advance, Sincerely, Ivan.
  13. Thank you for your reply - I've already tried, and succeed to downconvert it to LabVIEW 2015; everything seems to be working. I'd rather use it as plain lvlib, because I do not prefer using packed libraries... Thank you!
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.