I have been involved in migrating a BDE application from Delphi 5 to XE5, and it still uses the BDE. No problem. Not abandoned – so what is your point? The reasons they still use the BDE are
1 – No work to do other than figure out installing it on Windows 7 etc 2 – The BDE despite being a nuisance to install on workstations actually offers some real nice functionality – the update queries with GUI selectable fields that are candidates for being updated with ApplyUpdates is very nice to use. Alternatives meant enough recoding that they decided not to bother. 3 – That it still works after 15 years where other technologies have come and gone is neat. I found an interesting user survey on Delphi vs C#. http://vschart.com/compare/delphi-programming-language/vs/c-sharp C# scored more real good things (eg free versions for commercial use, documentation, HTML, Community, Jobs) But the most interesting ones to me were: Preference – Delphi scored 59% to C# 41%, Delphi works out of the box 65% to C# 35% Surprises or dubious areas are – C# rated well for iOS/Android development (is this so??) and better for performance than Delphi (really?) C# rated poorly for JVM support. Surprise surprise! From: Jolyon Smith The BDE didn't evolve. It was replaced and abandoned and applications relying on it then experienced difficulties arising from changes in the operating environment. It may not be possible to avoid this entirely. But you can hope to reduce the risk by ensuring that your applications employ technology that is an integral part of your operating environment, rather than relying on
_______________________________________________ NZ Borland Developers Group - Delphi mailing list Post: [email protected] Admin: http://delphi.org.nz/mailman/listinfo/delphi Unsubscribe: send an email to [email protected] with Subject: unsubscribe
