RE: [DUG] Delphi 8 Bug-Find-A-Thon

[Myles Penlington]

There is always a catch.   The solution is not totally generic and we were only using it to provide cached updates.   We have basically dropped the MIDAS technology due to certain bugs (that cannot be easily or consistently reproduced) to do with cached updates, nested datasets, changes to key fields etc and created our own replacement - that we can control. Of course these bugs may have been due to our changes to provider.pas, that MIDAS was unable to cope with correctly in all circumstances. A pity in reality, as the solution was quite simple and elegant to use.   A deciding factor was that there is no available source to the Midas DLL, hence we could not control the final quality of the product. Basically it has become policy that we only use components etc where there is source available. Once burned twice shy. Myles    -----Original Message----- From: Ross Levis [mailto:[EMAIL PROTECTED] Sent: Wednesday, 10 December 2003 21:00 To: NZ Borland Developers Group - Delphi List Subject: Re: [DUG] Delphi 8 Bug-Find-A-Thon Have you thought about offering the code to Borland, as they seem unwilling to fix the code themselves.  In all fairness they should pay you something for it.   Ross. ----- Original Message ----- From: Myles Penlington To: 'Trevor Jones' ; 'NZ Borland Developers Group - Delphi List' Sent: Wednesday, December 10, 2003 8:20 PM Subject: RE: [DUG] Delphi 8 Bug-Find-A-Thon Trevor, It's not a major problem, I have created solutions to this by changing the code in provider.pas - about 100 changed lines fixes the issue and a few changes in the datasets you use via the providersupport interface gets around most of the issues.   Of course if you want don't want to change the borland source you are out of luck.   Myles. -----Original Message----- From: Trevor Jones [mailto:[EMAIL PROTECTED] Sent: Wednesday, 10 December 2003 19:25 To: NZ Borland Developers Group - Delphi List Subject: Re: [DUG] Delphi 8 Bug-Find-A-Thon Richard,   I know that this is going to sound mean, but I have no idea how to sugar-coat it.     I use Interbase lots. Interbase is a Borland product.  Interbase doesn't like transactions that live for a long time.  All the TeamB members suggest that I use Client Datasets.      Client Datasets don't work with Interbase tables that use generators (int64 field type).      ergo Delphi doesn't work properly with Interbase.      I thought this was OK with D5 since that used Microsoft's understanding of variants, but now I find that D6 and D7 (which both use a different form of variant handling) also cannot use Client Datasets correctly, Borland components cannot use separate transactions for read and update, so effectively, Borland is selling a non-workable solution.     Can D8 do any better?  I can bring a notebook along, and try it out, but I don't want to be a wet blanket if it doesn't work.     So, I would love to be part of a bug finding mission, but finding the same old bugs would be a little boring.     I know that you have had run-ins with my Boss (he is a philistine) and with me (I am a smartass) but I am still an ardent Borland supporter.  Can you give any hint of whether or not this fundamental failure where Borland Delphi apps are not able to communicate sensibly with Borland Interbase databases has been addressed?     Will buy D8 and D9 and D10 'coz I believe in Borland ( and I dream in Pascal).     Will sell Interbase licenses galore as long as they are priced right.   Trevor

_______________________________________________
Delphi mailing list
[EMAIL PROTECTED]
http://ns3.123.co.nz/mailman/listinfo/delphi