I can't get this to run, there's a small kick in the CPU usage according to Task Manager but then nothing.
I have two previous versions of the same thing, all located as separate directories under C:\Portable Apps\SQL Utilities but I've also tried it from other locations (and downloaded it twice, just in case).
The other two work fine, and produce entries in Computer\HKEY_CURRENT_USER\Software\sqlitebrowser\sqlitebrowser, but the new one doesn't get that far.
Can anyone suggest what I should try next please.
Nobody?
I'm stuck because the versions of sqlite bundled with the older apps don't recognise tables created with new functions introduced in more recent versions.
Have I done something to upset someone, is there really no-one prepared to offer any sort of help or support with this? I can't get it to run at all, despite many attempts. Could someone at least confirm they're reading this and that it runs on their machine please.
I read almost every post, but I can't help diagnose your problem sorry.
I run on a Mac these days, and this week I am in a place with horrible internet and it would take me at least a week just to download a VM.
Something you can try though: instead of running it from the Platform or via the DBBrowserPortable.exe, please navigate down to the App/DBBrowser folder and run the DBBrowser.exe file directly (forgive me if the names or folder structure are not exactly what I am writing - I'm doing this completely from memory). This will bypass our portable bits, and if the program throws an error about a missing system component you should get to see it. That error message will help us determine if there is something missing/wrong on your end, or if our package may be missing something that has only recently been made a dependency.
Both the 64- and 32-bit versions fail because 'MSVCR120.dll was not found'. However a version of that file is included with SQLiteDatabaseBrowserPortable_3.10.1, and copying it across makes 3.11.2 work. So I think there is a file missing from the package.
Thanks very much
That's usually a pretty safe bet as to why an app fails from one version to the next when a dependency has been left out or not updated.
I've updated the post title so it gets picked up quicker by someone who can fix it!
This was fixed in the 3.12.x releases. They include the relevant VC runtimes.
Sometimes, the impossible can become possible, if you're awesome!