Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : INPR - Inprise to Borland (BORL) -- Ignore unavailable to you. Want to Upgrade?

To: Annette who wrote (3793)	12/21/1999 11:53:00 PM
From: Bradley W. Price	Read Replies (1) \| Respond to of 5102

I know the guys who use IB are probably pretty upset, but this doesn't seem to be a major product area for Inprise. I really don't agree that this is a bad move. Their future seems to be in tools/middleware. Why play if you are not dominant? Esp since it forces them to divert resources that are otherwise needed in other areas. I do agree that it should be made open source since there does seem to be a dedicated developer community. Making it free gets them a lot of good will with little downside.

To: Annette who wrote (3793)	12/22/1999 12:13:00 AM
From: David R	Read Replies (2) \| Respond to of 5102

Why not use MSDE (desktop SQL Server) and ADO? This is free, no royalties, and is a decent DB engine. If you have certain customers with greater needs, they just buy full-blown SQL Server. Your app is not even aware of the change. We are reasonably pleased with ADO/OLE DB. Perhaps this is why INPR is getting out of the IB business. Why try and sell what MSFT is giving away for free.

To: Annette who wrote (3793)	12/22/1999 7:32:00 AM
From: Bipin Prasad	Respond to of 5102

I wonder what the internal dynamics on Interbase is. However a java database (JDataStore) will be a good replacement since it is 100% Java and will run on multiple platforms. More more info, look at inprise.com Bipin Prasad

To: Annette who wrote (3793)	12/22/1999 8:11:00 AM
From: i-node	Respond to of 5102

Of course you probably know that with DBISAM, if you lose power to your pc while it is writing a record, it will corrupt the entire program? Actually, I don't know of a database product that doesn't suffer from this ill. Careful use of transactions is important. But as low-end databases go, DBISAM is remarkably stable. In fact, we have not seen one incident of database corruption since we changed to it; previously we were dealing with corruption on some customer's system on a daily basis. Stored procedures are not of interest to us. Referential Integrity is, but it is trivial to implement in code, so that's what we did. DBISAM is not a database of the character of IB; however, we have found it to be totally adequate for 1-100 users, and a vast improvement over using BDE.