My point still stands....you can test the application compatibility by copying the DLL into the app directory and changing the search order as I recommended. Did you try that?
The applications really need to compile sqlite in their app. That's the good fix here as has been pointed out (and something I always do). But good luck with that one. Michael D. Black Senior Scientist Advanced Analytics Directorate Advanced GEOINT Solutions Operating Unit Northrop Grumman Information Systems ________________________________ From: sqlite-users-boun...@sqlite.org [sqlite-users-boun...@sqlite.org] on behalf of Joe Winograd [j...@winograd.us] Sent: Sunday, January 15, 2012 1:52 PM To: General Discussion of SQLite Database Subject: EXT :Re: [sqlite] Incompatible versions of SQLite on same system > I don't really mind top or bottom post. I don't either, but it really should be one or the other; otherwise, you're jumping up and down to follow a thread. But that's because of the next point, where we disagree completely. > But the important thing is to trim anything you've quoted to just the useful bits. We don't need to see every single post to the thread every time someone adds a new post. I strongly disagree with this. In personal (one-on-one) correspondence, it makes sense, but not in email-based groups/forums, where members come and go at various points in time. A member should be able to jump into a thread and easily review the whole issue in one email. Having to go back and look at every trimmed message to piece together the entire thread is painful and, frankly, won't usually be done. This is also why top posting is better. The combination of the two (NOT trimming and top posting) means that a new entrant to the discussion can review the entire thread in one email (admittedly, having to page-up) while someone who has been participating in the discussion for a while can simply look at the top-posted most recent response(s). I think we actually have an example of the trimming problem in this thread. I may be wrong, and Michael Black may jump in to say I'm wrong, but a key comment of mine had been trimmed, viz., the <SQLite3.dll> doesn't even appear in the application directory of the two conflicting apps. If Michael had seen that in a non-trimmed message, I'm guessing he would not have said, "Can't you just copy the DLL into the application directory?" Come to think of it, by the time it got to Michael, "TurboTax" and "HP Connection Manager" (the two conflicting programs) had been trimmed out of the message. I would argue that those are "useful bits" of this thread. I think there are times when trimming is appropriate, but in most cases, I think that threads should be left intact. Just my humble, of course. Cheers, Joe -------- Original Message -------- Subject: Re: [sqlite] Incompatible versions of SQLite on same system From: Simon Slavin <slav...@bigfraud.org> To: General Discussion of SQLite Database <sqlite-users@sqlite.org> Date: Thursday, January 12, 2012 19:54:56 > On 13 Jan 2012, at 1:46am, Joe Winograd wrote: > >> Thanks for the clarification. > My pleasure. Triggers do generally work in the most useful way. Try coding > it and see if it works for you. > >> Btw, is bottom-posting the standard in this group? As you can tell, I'm >> rather fond of top-posting. Yes, I've ready many of the arguments why >> bottom-posting is better – I simply don't buy it. But I'll be happy to >> comply with group standards. > Bottom posting is the proper way to do it. I don't really mind top or bottom > post. But the important thing is to trim anything you've quoted to just the > useful bits. We don't need to see every single post to the thread every time > someone adds a new post. > > Simon. > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
