Stephen Posey wrote: > Sean Cross - CRM wrote: > >>> Cameron Cole wrote: >>> >>>> I read up on two crippling changes though. No native >>>> support for larger commercial databases namely SQL Server >>>> and Oracle (not including MSDE) and you can only have one >>>> Turbo version on a machine >>>> at one time so no Turbo C++ and Turbo Delphi on at the >>>> same time. >>>> > >> Stephen Posey Wrote: > >>> The first I can see if there's a (possibly pricey) add-on to >>> provide the DB functionality; and there's always the >>> aftermarket tools. >>> >>> The latter is ridiculous, I sincerely hope they're not >>> seriously considering doing that. >>> >> That is apparently a function of the design (you can't install >> Delphi 06 Pro and Enterprise on the same machine either) >> rather than marketting. You can always use vmware. >> > > I might buy that as an excuse if historically it had been > impossible to install concurrent versions of Delphi, C++Builder, > and JBuilder all on the same machine, which is clearly NOT the case. > > Anyway, I've successfully had all versions of Delphi 1..6 and > C++Builder 1&3..5 installed on the same machine; which I realize > isn't quite the same thing, but what's stops you from installing > both Pro and Enterprise? > > Not that I ever tried (never had occasion to) and it admittedly > seems a bit silly (why bother with Pro if you have Enterprise?); > but if you install them to different locations what keeps them > from working? > > I'm pretty familiar with Delphi's registry usage and I'd expect > both would end up reading from the same keys obviously, but that > shouldn't present any particular problems that I can think of off > the top of my head, just changes in one IDE would show up in the > other Since both versions of D6 would read from the same registry entry they'd need to be located into the same directory structure! The registry contains stuff about paths as well as info about colors, components and other less important things. So installing two editions of the same product on the same machine would fail - but I think that's true for ANY software product with multiple editions for the same version.
On the other hand different Borland products (including different versions of the same product: D5 / D6) use different registry keys. Sure they'll all routed into the same big tree but they do use different keys. In the end I think installing different Turbo XXX products would be similar to installing different current Borland products not similar to installing different editions of the same product. If there is such a limitation (only allow one version of Turbo XXX on any given machine) I'm sure it's a beta-bug OR some well-crafted Borland feature, not a side-effect of registry storage. __________________________________________________ Delphi-Talk mailing list -> Delphi-Talk@elists.org http://www.elists.org/mailman/listinfo/delphi-talk
