I made the change only to see if all the JET*.tmp files are related with Avast rather than other programs. Now that all the JET*.tmp files are gone, I only see avast4 folder in the temp folder. However, is there possible side effect for this change?
If you ask which is better ODBC or XML? I’ll say that for the Home version, they are equal.
For the Professional version of avast!, XML is missing some functionality (compared to ODBC), so switching avast! Pro to XML storage is not a good idea: ODBC makes it possible to store the past sessions in the Professional version - which is not possible with XML. Appart from this, Enhanced User Interface behaves strange when switched to XML storage - when a task is started, another instance of it appears in the list (of the tasks, not of the corresponding sessions!). Alwil did not explore the problem deeper yet, so it could be a bug or just something caused by the inability to store additional info in the storage. Right now, XML storage is currently considered just a backup option for avast! Home.
On contrary, to URL blocking (WebShield provider) switch to the XML storage allows a higher limit of characters. The path could have up to 1000 characters.
I’d been wondering about that myself, though I’ve seen no problems since switching. Thanks, Technical, for the answer, and Umath for asking.
Yes, thank you for the reply, Technical.
Avast is “one of the most configurable anti-virus software”TM but if we don’t know what a certain option will do, it’s meaningless or it may rather end up with a trouble. It’s nice for Avast team to keep this forum to share their knowledge with users and let us do the same each other.
FWIW, on my Win98 system, which has avast! home edition, I had to resort to using XML, as the ODBC method didn’t work well. The XML method works great for me.
On my XP system, ODBC works fine.
So, that’s the reason of the forum: help and knowleage share 