Devart Forums

Hi. If you missed my post on a similar issue, please see it:
viewtopic.php?f=4&t=37035

And, there is an excellent modern freeware SEE-compatible SQLite encryption library named SQLite3MultipleCiphers available here:
https://github.com/utelle/SQLite3MultipleCiphers

I'm using it with dotConnect for an application -- works well.

Good luck.

-C

Thanks.

Hello. The dotConnect Universal documentation in Provider-Specific Notes mentions the "most important connection string parameters". Is there a way to enumerate the full parameter list in code? Thanks.

Thanks very much for that detailed explanation. Once I applied your notes, all is well. I used an "x86" subfolder (from app location) containing the FSEE sqlite3.dll file, and a connect string similar to this...

Provider=SQLite; DataSource=C:\Temp\Database.db; Encryption=SEE; Password=aa

Works perfectly. Seems FSEE is a viable free option for encryption with dotConnect.

Thanks again!

Is it possible to have dotConnect Universal when used with dotConnect for SQLite to use a provided sqlite3.dll library, as can be done in UniDAC?

I'm trying to interface to a freeware SEE-compatible encryption library (shenghe/FreeSQLiteEncryption on Github). The error reported is that it cannot find a API named sqlite3_key in sqlite3.dll. It seems Universal always wants to load the sqlite3.dll that is in the Windows System32 folder, instead of the one in the current app folder. Even with deleting the Windows one, it will still not find a local one.

I was able to use FSEE with SQLite Expert Professional to easily manage encrypted database, so its easy and seamless.

Could we have FSEE officially supported as another encryption option in Universal?

Thanks.

I see from a prior post that the JSON1 SQLite loadable extension has been included/enabled for the dotConnect product. Can this also be done for UniDAC? Thanks.

I'm hoping to hear something on this issue. I have a planned release coming soon and would like to see this addressed. Thanks.

Do we have any thoughts on this? I hoping for a resolution. If a fix will appear in the next release, and that release is months away, I'd hope to get an interim build. Thanks.

I recently upgraded to 6.3.13 for XE7. In the VirtualTable editor, for an existing record, for a memo field, there is normally a small button that leads to a popup text editor. This button is missing. In all other aspects, the product is working well. Thanks.

Thanks. Your mention of that caused me to inspect things a bit, and yes, there are no MS Access ODBC drivers that handle the .accdb format.

There may be more than one solution, but I chose to install the Microsoft Access Database Engine 2010 Redistributable (available in 32 and 64 bit) from https://www.microsoft.com/en-gb/downloa ... x?id=13255. This solved the problem. Thanks.

I'm now using only the components on a form. I had tried your suggestion already -- did not work. I've tried it again -- same. I have now created a new 2013 .accdb file and the same things occurs with that one. The only difference is that when I change the specific option to dvAccdb, the message changes to "[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified.".

A prior version of UniDAC worked fine. Now working with 6.3.12 under XE7. I can open a particular .accdb in Access 2013, but trying it with UniDAC (in an app or just with components) does not work. It displays the message "[Microsoft][ODBC Microsoft Access Driver] Cannot open database '(unknown)'. It may not be a database that your application recognizes, or the file may be corrupt..". Trying it with an .mdb file works fine. Please have a look. Thanks.

Yes, after I installed this SDK, UniDAC detected the ODBC driver and had no trouble getting to the ASE server. Thanks.

The SAP download/search facility makes it very difficult to find what is needed, and there was a change between ASE 15.x and 16.x on what clients are available and how they are distributed. The needed client, if you want it separate from the ASE server install, is called the "SAP SDK for Adaptive Server Enterprise".

However, the magic bullet is simply the SAP Store. There one can find trials for all of the late version clients (don't know why it's a trial vs. just a download).

Link...
https://store.sap.com/sap/cpa/ui/resour ... 73286474-0

Thanks.

Few questions please on getting UniDAC 6.0.2 for XE7 to connect to Sybase ASE 16.0.

I've installed ASE on a virtual machine and have confirmed it's up and able to query from that machine, etc. I'm now trying to access that server from another machine on the network using UniDAC.

Questions...

1. Past posts seem to indicate a client has to be installed on the non-server machine. Is a client required, or is just a registered ODBC driver required?

2. A past post also seems to hint at support was coming for dealing with ASE sql.ini files. Was this ever delivered? I checked the history and could not reference it.

3. After trying to work with a registered ODBC driver copied from the ASE 16 install, I can get UniDAC to recognize that the driver is present -- but no success getting a connection, either via UniDAC or with testing from a DSN. I'm now in search of said client. Various posts say it's part of the "SDK", others say it's "PC Client", and yet others say that it's part of the ASE 16 full install. Can anyone shed any light here?

Thanks in advance.