Excellent point!
I guess there's no solution that the end-user can deploy in this case. It's
not even clear to me how the HP and/or Intuit programmers can solve the
problem, since I replaced the HP Connection Manager <sqlite3.dll> with the
latest one and TurboTax doesn't even have a <sqlite3.dll> anywhere in its
directory structure and there isn't a <sqlite3.dll> in any system directory
and when the <dbUpdate.exe> fails, there isn't even a <sqlite3.dll> that's
been loaded in memory. Regards, Joe
-------- Original Message --------
Subject: Re: [sqlite] Incompatible versions of SQLite on same system
From: Jean-Christophe Deschamps <j...@antichoc.net>
To: General Discussion of SQLite Database <sqlite-users@sqlite.org>
Date: Mon Jan 16 2012 18:18:06 GMT-0600 (Central Standard Time)
At 01:08 17/01/2012, you wrote:
´¯¯¯
Richard, Simon, and you are seeing eye-to-eye on this. Earlier in the
thread (since trimmed, of course), it was stated that SQLite was designed
to be tiny so that each app could include the entire system without
draining resources significantly (this would solve the problem of apps
stepping on each other with different versions of <sqlite3.dll>). So if
that's the case, why not kill the distribution of <sqlite3.dll> and force
the developers to do it the right way? Regards, Joe
`---
That would preclude use of SQLite in situation where no linking is
possible, like many scripting languages, etc. That it is allright for
your current use cases doesn't imply it's convenient or even possible for
others.
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
