Re: Looking for transaction oriented database to compile into .EXE

In article <01bcb5f0$86803960$46f39ecd@mail> "Will Estes" <wenews@usc.com> writes: >I'm looking for a transaction-oriented database that I can compile directly >into a Windows NT server, preferably without a need to pay royalties. >The only product I have found so far that even meets the technical >requirement is the run-time version of Sybase SQL Anywhere. Are there any >other products that I should consider for an in-process transaction >database that will ship with a commercial application? Definitely look at Borland's Interbase product. It is a "sleeping beauty," although it is not royalty-free. I am not sure of the architecture of your application. If your application is the server, then it is the only client of the database engine and choices such as Microsoft's Jet and Borland's BDE are good candidates. Each user connection to your (one) server program could open a connection to the database. But look very hard to see that you are not reinventing the wheel. It is easy to spend thousands of dollars to help users save hundreds. And it may not be worth it in the long run, especially as users' needs grow and they want to standardize on a server and be able to switch all their apps (including yours) from one server to another. If your application becomes "the odd man out," it starts looking "obsolete" sooner than it should, and *you* are the one who has to keep advancing its technology curve. If, on the other hand, you build your application to use a very standard middleware layer, e.g. ODBC or DAO or BDE, and, say, you price your app with and without a server included, then you give the user reasonable pricing options while also leaving them in the driver's seat. Be sure, of course, that your pricing arrangements cover all of your costs necessary to provide support, customization and so-forth.