My dozen or so custom SQLite functions are not useful to anyone else, as they are very specific to my application's data. (Never mind the fact that they would not be accepted by DRH anyway).
I commonly swap different sqlite3.dll versions in and out between runs while using Mike Cariotoglou's (excellent) SqliteExplorer and have no difficulty at all. I'm not sure why others have such problems will DLLs. But I guess the number of satisfied users of the statically-linked SQLiteSpy outnumber the users requiring a custom/older/newer sqlite3.dll DLL by 100 to 1, so it's my loss. :-) --- Ralf Junker <[EMAIL PROTECTED]> wrote: > Hello Joe Wilson, > > the build-in database engine is a much praised feature of SQLiteSpy. It > simplifies the life of > many users, and mine as well, since there can be no incompatabilities with > wrong DLLs and > versions. > > I am sorry that you can not use SQLiteSpy with your custom DLL. Maybe you > would like to > contribute your changes to the SQLite sources, so they can become part of > SQLite and SQLiteSpy > as well? > > Apart from that, I monitor the development of SQLite closely and will always > update SQLiteSpy to > the latest version of SQLite as quickly as possible. > > Regards, > > Ralf > > >I'm not sure if this is a good feature, though: > > > > Built in SQLite Engine > > SQLiteSpy comes as a single file executable with > > the SQLite database engine already build into the > > application. There is no need to distribute any DLLs, > > which makes SQLiteSpy easy to deploy with customers. > > > >I have a custom sqlite3.dll so I would not be able > >to use my databases with your app. Nor would your > >users be able to upgrade to newer versions of > >sqlite3.dll. > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
