Re: Alpha 5 V8 vs MS Visual Web Developer
Edit: One second look, this isn't really applicable to the original question but it may still provide some useful insights.
An answer to this was alluded to earlier by DaveM but let me add my 2 (4?) cents.
You've made the typical statement of concern that it is a "proprietary" system. In fact, the real issue isn't the fact that the underlying database is "proprietary"; it's the fact that the actual application is "unique".
As you pointed out, the issue is that "the programmer is no longer around, so who do they go to for help?" This will be true no matter what underlying program is used or who builds it. The real issue shouldn't be A5 vs. .net or Access, or Oracle, or any other database. What makes it unique is that it was designed and built specifically for one company.
ANY program that is built for one company is unique no matter what underlying program or programs were used to build it. And, since it was built for only one company, it was probably built by one person or a small team that will probably not be around as long as a large company like Intuit (QuickBooks). HOWEVER, even if you could get someone at a large company like Intuit to build your custom application, there will be support problems down the road because the original people that designed it will probably leave or get re-assigned and new people will have to figure out what the original designers were doing. In fact, assuming the large company would even do it, the problem is likely to be worse with a large company than it would be with an independent developer. If it was done by an individual developer, someone else may still have to figure out how it was done but that doesn't mean that nobody could do it - especially if your developer documents the "why" part of the application. (Many people document the field names, field rules, and what was on each form but I can get all that very easily. The really important thing is to document any special logic in the scripts. Think in terms of, "I did this because..." and whenever it's not obvious, spell it out in a comment.)
So, the issue is with a custom built application and that issue will be true no matter who builds it or what they build it with.
My recommendation has always been, "If you can find a canned program that meets your needs, BUY IT!" However, if someone can't find what they need in a canned program and wants to have someone build them a custom program, WHO creates it for them is much more important than WHAT underlying program is used to build it. I've seen some very good applications in A5 and some very bad ones. And the same is true with other databases. A good developer will do a good job no matter what underlying program is used. And the corollary, of course, is: A bad developer will do a bad job no matter what underlying program is used.
I know of one A5 application that someone paid about $10,000 for and it was so bad that I would have been ashamed to say it was mine at any price. I've also heard of applications built with databases that are more "mainstream" that don't work even after spending many thousands of dollars. (In fact, I heard of one application using mainstream programming that was released then pulled from the market because it didn't work even after spending well over a million dollars on it. I'm sure they'll try to fix it - they almost have to after spending that much money so far.)
Some of those "rebuilt databases" have been listed on this A5 message board because they were eventually rebuilt, usually in less time, with A5 - and they actually worked. If my memory is correct, in one case $80,000 was spent on a program before it was shelved and then redone in A5 in a matter of just a few weeks.
As for the question of, "What happens if you get hit by a truck?" In addition to the above comments, you might point out that, based on the amount and quality of assistance available from this message board, there are plenty of good developers out there who will make sure they get the assistance they need.
Another interesting point is that they could probably even contact one of the co-founders of Alpha and get some recommendations regarding developers who could handle their type of application. Try to get that from Microsoft!
So, if you can't sell the use of A5 to a potential customer on this basis, you probably don't want that customer anyway because they will never be happy with anything you do.
Edit: One second look, this isn't really applicable to the original question but it may still provide some useful insights.
A friend pointed out to me that some of these people have been burned in the past by "proprietary" systems...the programmer is no longer around, so who do they go to for help?
You've made the typical statement of concern that it is a "proprietary" system. In fact, the real issue isn't the fact that the underlying database is "proprietary"; it's the fact that the actual application is "unique".
As you pointed out, the issue is that "the programmer is no longer around, so who do they go to for help?" This will be true no matter what underlying program is used or who builds it. The real issue shouldn't be A5 vs. .net or Access, or Oracle, or any other database. What makes it unique is that it was designed and built specifically for one company.
ANY program that is built for one company is unique no matter what underlying program or programs were used to build it. And, since it was built for only one company, it was probably built by one person or a small team that will probably not be around as long as a large company like Intuit (QuickBooks). HOWEVER, even if you could get someone at a large company like Intuit to build your custom application, there will be support problems down the road because the original people that designed it will probably leave or get re-assigned and new people will have to figure out what the original designers were doing. In fact, assuming the large company would even do it, the problem is likely to be worse with a large company than it would be with an independent developer. If it was done by an individual developer, someone else may still have to figure out how it was done but that doesn't mean that nobody could do it - especially if your developer documents the "why" part of the application. (Many people document the field names, field rules, and what was on each form but I can get all that very easily. The really important thing is to document any special logic in the scripts. Think in terms of, "I did this because..." and whenever it's not obvious, spell it out in a comment.)
So, the issue is with a custom built application and that issue will be true no matter who builds it or what they build it with.
My recommendation has always been, "If you can find a canned program that meets your needs, BUY IT!" However, if someone can't find what they need in a canned program and wants to have someone build them a custom program, WHO creates it for them is much more important than WHAT underlying program is used to build it. I've seen some very good applications in A5 and some very bad ones. And the same is true with other databases. A good developer will do a good job no matter what underlying program is used. And the corollary, of course, is: A bad developer will do a bad job no matter what underlying program is used.
I know of one A5 application that someone paid about $10,000 for and it was so bad that I would have been ashamed to say it was mine at any price. I've also heard of applications built with databases that are more "mainstream" that don't work even after spending many thousands of dollars. (In fact, I heard of one application using mainstream programming that was released then pulled from the market because it didn't work even after spending well over a million dollars on it. I'm sure they'll try to fix it - they almost have to after spending that much money so far.)
Some of those "rebuilt databases" have been listed on this A5 message board because they were eventually rebuilt, usually in less time, with A5 - and they actually worked. If my memory is correct, in one case $80,000 was spent on a program before it was shelved and then redone in A5 in a matter of just a few weeks.
As for the question of, "What happens if you get hit by a truck?" In addition to the above comments, you might point out that, based on the amount and quality of assistance available from this message board, there are plenty of good developers out there who will make sure they get the assistance they need.
Another interesting point is that they could probably even contact one of the co-founders of Alpha and get some recommendations regarding developers who could handle their type of application. Try to get that from Microsoft!
So, if you can't sell the use of A5 to a potential customer on this basis, you probably don't want that customer anyway because they will never be happy with anything you do.
Comment