viSci Posted Sunday at 01:27 PM Report Posted Sunday at 01:27 PM (edited) I realize this SQLite LIbrary (by ShaunR) is pretty ancient so not surprised there maybe some dll updating required but I thought I would inquire. I have used it many times in the past and have come to appreciate its performant well crafted design. Edited Sunday at 01:29 PM by viSci Quote
ShaunR Posted Sunday at 01:55 PM Report Posted Sunday at 01:55 PM The SQLite API for LabVIEW was retired 6 years ago (at version 5.0.0). Quote
viSci Posted Sunday at 05:44 PM Author Report Posted Sunday at 05:44 PM (edited) That is considerably more modern then my v1.3.1, I would give it a go if you could make it available... Edited Sunday at 05:45 PM by viSci Quote
ShaunR Posted yesterday at 07:38 AM Report Posted yesterday at 07:38 AM If you have a commercial waiver then there is limited residual support but apart from that, you should be looking to transition to an alternative product. Quote
hooovahh Posted 23 hours ago Report Posted 23 hours ago There are several SQLite libraries on VIPM.io. I personally use the one by JDP Science, but a few others also look promising. Changing over will obviously take some time finding and replacing one API for another, especially if there are differences in design choices in how they each implement similar functionality. Quote
viSci Posted 23 hours ago Author Report Posted 23 hours ago Thanks. I have already started porting to JDP SQLite. I should have done that a long time ago. Quote
ShaunR Posted 13 minutes ago Report Posted 13 minutes ago 22 hours ago, viSci said: Thanks. I have already started porting to JDP SQLite. I should have done that a long time ago. If you didn't use the encryption then you could use the SQLite binaries from SQLite.org to keep you running while you transition. I can't remember off-hand if it was supported in 1.3.1 but adding AES=NONE to the project conditional symbols enables the use of vanilla SQLite binaries (i.e. comments out encryption function calls). That said, I expect the issue with LV2025 is probably to do with calling parameters rather than the binary itself because V5.0.0. seems to work fine with LV 2025 & 2026. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.