john doe

There is an example in the manual 2.7.1 (pg 227 HyperSQL User Guide HyperSQL Database Engine 2.7.1): CREATE TRIGGER t BEFORE UPDATE ON customer REFERENCING NEW AS newrow FOR EACH ROW BEGIN ATOMIC IF LENGTH(newrow.firstname) > 10 THEN SET newrow.firstname = LOWER(newrow.firstname); END IF; END This example does almost what I need, because it allows a change to be made to the table. I would like to modify it to something like: CREATE TRIGGER PERSON_BU_NEW BEFORE UPDATE ON "tPerson" REFERENCING NEW...

This cannot be the case. Windows 11 vs Ubuntu 20.04 Improper dismount by Windows; not caused by me. Did not re-mount, but shut down Windows. USB stick to Ubuntu, now stick is Read Only. There must be a way to force the issue under Ubuntu. Reason: Not always access to Windows machine, but always to Ubuntu machine. Portable data sticks are vitally important to my work.

Infrequently, Windows 11 indicates that the connection has been broken between an encrypted USB stick 256GB. After the so-manieth time locking up, windows indicates "D:\ The directory name is invalid." even after a restart of Windows 11. So now there is a 'left over' on the computer that does leads to Windows indicating this. The placement of the left-over is not known. Even with an other USB stick of 512GB, Windows indicates the same. When removing/uninstalling VC from the computer, Windows asks...

When using VC via The Terminal, it operates appropriately. It used to be that the following would work for the GUI as a workaround: Work around 1. sudo mv /usr/bin/veracrypt /usr/bin/veracrypt.bin 2. create a bash script with the following content by typing sudo nano /usr/bin/veracrypt and pasting the following content: ◦ #!/bin/bash ◦ ◦ set -e ◦ ◦ /usr/bin/veracrypt.bin --use-dummy-sudo-password $* 3. make the script /usr/bin/veracrypt executable: sudo chmod +x /usr/bin/veracrypt Please advise,...

After update to latest version, the standard way of adding a program to 'the Dash' is not applicable to VeraCrypt 1.25.4. It appears not to be possible to add it to 'the Dash' Dream

Ubuntu 20.04 has to many issues and did therefore downgrade back to 18.04. There are no problems there. Did you find anything with a clean install of 20.04? Dream

Using the Terminal to access VeraCrypt, everything is as expected. Using the GUI, I have to enter the SUDO password 3x. This is the same as was with 18.04, as I remember. There was an update issued to fix it. How did you install 20.04? I did it via the upgrade protocol. I do not know what happens with a fresh install of 20.04. Dream.

Sorry, but that does not solve the issue. Having gone back to 1.24upd4, VeraCrypt works as expected when running via Terminal. I remember having the same type of issue updating to Ubuntu 18.04, coming from 16.04. VeraCrypt needed an update. As having this issue, do I continue under a Ticket 353, or do I stay here under 'Technical Topics'? Dream