Quote:
Originally Posted by BookJunkieLI
@BetterRed - I took a look at the QV changes but honestly I didn't really understand what they actually meant so no idea if they're the cause of the sudden change.
|
I couldn't see anything obvious there either.
Quote:
Originally Posted by BookJunkieLI
Question, would running the Restore Database from the command line be faster and/or less prone to the dreaded Not Responding?
|
Not sure about the faster part, but you wont get a "not responding' at the command line, I think that's because cli proggies aren't in the message loop. I've never got a foggy screen in cmd.exe - now it's bound to happen
Suggestion: If the database rebuild doesn't solve the problem, install another edition (portable, 32bit whatever) for Version 2.18 and see if you get the same problems. If you don't then it would cast suspicion back on 2.19, but apart from QV (which isn't immediately obvious as a culprit either - aside from the fact that it nicked my ctrl/alt/p
) none of other changes look remotely related. .
BR