On 5/5/06, Robert Simpson <[EMAIL PROTECTED]> wrote:
- You never have to worry whether a newer sqlite3.dll will work with an older wrapper, or a newer wrapper will work with an older sqlite3.dll. For example, checkin 3040 and several other sqlite checkins which changed the behavior of API calls. Just copying the newer sqlite3.dll could've potentially broken your app using an older wrapper. By combining them, there's less opportunity for someone to accidentally screw something up.
You might consider this: Always copy old style windows dll's to the directory where the application that uses them resides. This ensures you run that particular dll with that application even if there are multiple different incompatible copies on the same machine. Yes, this negates all the advantages of having a dll. I personally prefer less "fragility" at the cost of a little disk space and memory. Those are both cheap compared to support calls. New style dll's preclude doing this since they're registered.
