Re: Captain Jake's Top Ten List of what I'd like to see in the nextversionofDelphi

Randy Magruder wrote:
Problem is, you have NO idea how well it's going to work with the
database, what performance issues there are, whether the evolve
database strategy will work for you, etc...unless you have the
Enterprise product.

Yep...and developers don't like to feel like they're being constrained
in any way. I know that I wouldn't trust it until I used it in as
similar to production environment as possible.

I repeat: I think that the way that ECO scaled down is not going to
significantly improve ECO adoption. Databases are not enterprise only.

Agreed 100%.

--
Brian Moelk
Brain Endeavor LLC
bmoelk@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
.

Relevant Pages

  • How to Perform SQL Select on a DataSet
    ... I am in the process of making a desktop version of an enterprise product. ... I have re-created the database tables necessary into XML files and store ... them on disk. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Datebase needed for tracking of drugs for a fire department!
    ... including for MS Access database development. ... There are good developers, don't get me wrong, but one has to ... Excel makes you think in math calculations. ... Shelf life of the drug could be loaded once and then access ...
    (microsoft.public.access.tablesdbdesign)
  • Re: WHY
    ... I've been working a lot longer than that LoL ... re-creating the same spreadsheet, ... > I'm sure the database admins do all the work at, say, Boeing and Airbus, ... > Or perhaps you meant implicitly to restrict your remarks to developers. ...
    (microsoft.public.excel)
  • Re: Transformable v. regular subscriptions
    ... Director of Text Mining and Database Strategy ... RelevantNOISE.Com - Dedicated to mining blogs for business intelligence. ... "Hilary Cotter" wrote: ...
    (microsoft.public.sqlserver.replication)
  • Re: compilers
    ... Pick is superb for the database and the business rules, ... I'll be happy to look hard at OpenQM if I ... This means that whatever back-end database I have to use needs to support ... positions that I do because they are developers, ...
    (comp.databases.pick)