Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 5 of 5 total |
A V2 question |
Fri, Apr 18 2008 2:19 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Tim
Is V2 when I finally no longer need to keep sorting out my packages that require ElevateDB? Roy Lambert |
Fri, Apr 18 2008 7:01 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Roy,
<< Is V2 when I finally no longer need to keep sorting out my packages that require ElevateDB? >> It must be too early for me - could you explain further ? -- Tim Young Elevate Software www.elevatesoft.com |
Fri, Apr 18 2008 9:26 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Tim
><< Is V2 when I finally no longer need to keep sorting out my packages that >require ElevateDB? >> > >It must be too early for me - could you explain further ? When I develop a component that relies on ElevateDB I have to change the package (.dpk) where it references ElevateDB eg requires vcl, vcldb, bdertl, VclSmp, TMSD2006, rtl, dbrtl, inet, designide, xmlrtl, vclactnband, vclx, adortl, tee, vcljpg, edb109b2006run; <<<<<<<<<<<<<<<<<<<<<< Roy Lambert |
Fri, Apr 18 2008 2:08 PM | Permanent Link |
Lance Rasmussen Jazzie Software Team Elevate | Roy,
That's one of the only things that I don't like with the naming conventions of EDB. I have a lot of 3rd party components and some I've brought in the DCP requires for EDB. So when a new minor version is released, I have to go into all the components that reference them, change the reference, then rebuild. Unless financially out of sight, I make every effort to obtain the source code editions to all components, which then allows me to do this. But when you don't have source code, you have to wait and bug the other component company to get the EDB update, build it, then provide an update. At least Tim is using Build numbers, so it's less frequent an issue than it could be. However, if I had my drothers, I would have naming to a major version number only. Lance "Roy Lambert" <roy.lambert@skynet.co.uk> wrote in message news:B940620C-2FC6-4F53-9B5C-8B1AA1D869A7@news.elevatesoft.com... > Tim > >><< Is V2 when I finally no longer need to keep sorting out my packages >>that >>require ElevateDB? >> >> >>It must be too early for me - could you explain further ? > > When I develop a component that relies on ElevateDB I have to change the > package (.dpk) where it references ElevateDB eg > > requires > vcl, > vcldb, > bdertl, > VclSmp, > TMSD2006, > rtl, > dbrtl, > inet, > designide, > xmlrtl, > vclactnband, > vclx, > adortl, > tee, > vcljpg, > edb109b2006run; <<<<<<<<<<<<<<<<<<<<<< > > Roy Lambert |
Sat, Apr 19 2008 9:40 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Lance
>At least Tim is using Build numbers, so it's less frequent an issue than it >could be. However, if I had my drothers, I would have naming to a major >version number only. Snap for the external stuff. Internally, and showing in the IDE have a "full" version number Roy Lambert |
This web page was last updated on Tuesday, April 30, 2024 at 03:55 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |