|Home » Elevate Software Blog » Don't Let This Happen To You...|
|Tags: ElevateDB, DBISAM, Distribution, Support Costs||Permanent Link|
|Comments (3)||You must be logged in to comment|
|Daniel Kram said...||Reply|
I am of course not sure of what point-of-sale, or POS, software you downloaded, however, I have downloaded a POS package and it behaved exactly as yours.
In my case, I dug around the forum for the software and found I could download the demo DB and tweak a setting to "complete" the installation, however, as non-tech potential Customer, I would not have gone to such lengths.
The embedded aspects of ElevateDB is one of the primary reasons we chose this product. Is MySQL or SQL Server more robust or more powerful: debatable, but are they bigger - absolutely.
Summary: Developers - strongly suggest to Management to have the software tested in as many situations as possible even if it delays delivery a little. Delayed delivery is better than losing Customers.
|Tim Young [Elevate Software] said...||Reply|
I can't say the name, for obvious reasons, but it was a nice package apart from the bulk and the installation issue. The hard part to understand is the logic behind using a database engine that is so overly bulky for something like a hair salon. I think it's just a case of the company trying to make things easier on the development side (SQL Server is the default database for everything in Visual Studio), and ending up making things harder for the customer (and the support staff).
|David Cornelius said...||Reply|
This very thing (trying to get SQL Server Express to work) is what moved me to build an application with ElevateDB.
When starting development on the application that my customer has now been using for a few years, I hadn't yet decided on the underlying database but had been reading a lot about SQL Server Express. I bought a book about SSE and read many articles about how to configure and install and setup instances using their monolithic engine. Not only did I have SSE already installed, but I had another application installed that had added a database instance for its own use. How hard could it be for my application to add one? Well, it turned out to be a nightmare that I could never quite figure out (too many different potential scenarios to account for). I knew there had to be a better way.
I had used DBISAM in a previous application and decided to check out ElevateDB for the new one. It turned out to be a very good solution and I have been extremely happy with the small footprint and ease of development and deployment with Elevate Software products. (The support is terrific, too!)