@Clemmins; I'll read over that a bit more carefully, and see if there are any hints on HOW-TO in there. I'm using the free version of Berlin ATM, and when I win a small lottery, I'd love to upgrade as I REALLllly miss the code reformat functionality of previous versions. (Previous employer gave me, directly, a license for D5 and 7 -- Can't tell ya in how many places I've got those codes stored. ;) )
@Ryan; As a developer, who's only done code always for for myself, previous employer for in-shop work only, and a few friends, I'm in both camps for "Use DLLs" and "Single EXEs". I agree with both sides of the argument, but, my mind pertaining to the distribution of SQLite3 DLLs by 3rd parties leans me towards the Single EXE methodology, at least for my applications. Even my personal rig has been (temporarily) messed up due to a 3rd party app that decided its version of the SQLite library is more important than what existed before. Knowing that capability exists for 3rd parties to steam roll a working machine into a partially working machine, this event has affected how I build and stage things in a couple of ways, but that's another story. When performing upgrades to my software, and distributing it, typically, my EXE code is being updated as well anyways. If the DLL has to be updated as well, well, then, that's great, and that DLL would be part of the distribution anyways. I understand that for MASSIVE application packages, where many EXEs rely on single DLLs, yeah, then DLL methodology is probably the way to go, as a small 50k file to fix a problem for many applications in the package, makes perfect sense. However, working with already a single do-everything-it-needs-to-do-under-one-roof kind of application, I'm able to see the advantages on BOTH sides of the fence. Due to the unknown recipient machines, in regards to availability of SQLite3 being present at all, the correct version that supports my code, and other varying details that I'm overlooking about an unknown entity, having what I know works in one single source, and it dealing with everything internally makes more sense to me. Sometimes, I even build in the JPGs for icons, mouse cursors, sounds, and all that DIRECTLY into the EXE, as I don't want people to change a mouse click into a train horn or whatever. (As fun as that is ;) ) Don't get me wrong. Merritt to BOTH sides of the coin. Right now, I just don't have the option of a truly single EXE with baked in DB engine capabilities, and I know that I miss it. If I can figure out the OBJ methodology, and get the wrapper I use ( http://www.itwriting.com/blog/articles/a-simple-delphi-wrapper-for-sqlite-3) to work with the OBJ or DLL based on build conditions, I'm all for it. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
