Thanks, Richard and Keith for your very helpful information. I suspected that programmers could "hide" custom collations away from prying eyes using the API. I've scanned all files in the software's Program folder using a content search for those collation names (Super Finder XT) and found nothing, neither in the sqlite3.dll nor any other files. Apparently once compiled they become undetectable. Since nothing in the database seems to require them once the error message is dealt with, this is a non-problem.
I'm going to stick with my method of simply overriding the collation with a built-in one in my scripts. Since the content of the database changes almost daily, the other methods you've so kindly mentioned seem to this novice like they would need to be done with every new backup copy of the real database (to which I have no access), and so would be as burdensome as my original workaround. Just putting the override in the script is a one-time change, no matter how many times I export a backup from the software to work on. Feel free to correct me if I'm wrong. Still, your suggestions were part of my SQLite learning process and are greatly appreciated. Cautions about the effects of overriding collations on key columns are duly noted, thanks for explaining that, Keith. Finally, thanks to both of you for pointing me to some additional documentation. I consider this thread resolved, but as a newbie to the mailing list I don't know if I need to do something to close it... Jim _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
