Hi Tim,

I'm sure you're sick of this question but do you have an updated
timeframe for the release of v5?  No pressure, we're just trying to
decide when to release our BDS2006 compiled app.  If it's coming out
soon we'd like to release both upgrades at the same time.  Are we
talking days, weeks, months?  Any hint would be helpful.

Thanks,
Al

Al,

<< I'm sure you're sick of this question but do you have an updated
timeframe for the release of v5?  No pressure, we're just trying to decide
when to release our BDS2006 compiled app.  If it's coming out soon we'd like
to release both upgrades at the same time.  Are we
talking days, weeks, months?  Any hint would be helpful. >>

I'd rather not say at this point.  It's getting closer every day, but I made
the mistake of stating some estimates in the fall and now I've got egg on my
face.  Basically, we sometimes have to go back and rewrite stuff if it isn't
right (and we did in December), and so estimates aren't worth much once that
happens.  I simply will not release the product until it is ready, so the
release date will always suffer before the quality.

I would basically plan your application around not having ElevateDB in the
timeframe that you would wish.  That would be the safe and prudent course of
action.

--
Tim Young
Elevate Software
www.elevatesoft.com

Thanks for the response Tim.  I think I speak for most of us that we'd
rather have a stable product released later than a buggier version
released sooner.  We love your stuff and we're looking forward to
seeing the new version when it's ready.

Al

Tim,

I have two projects that I am rewriting/want to rewrite with
DBIsam/ElevateDB. I have been holding off hoping for DBIsam5/ElevateDB
but I really need to get started on them.

My question is, will it be fairly easy or difficult to convert DBIsam
v4.x tables to ElevateDB tables? If it would be like converting from
another database, then I might as well wait although the projects will
take a big hit on my goals and objectives this fiscal year. However, if
the base tables conversion is straight forward enough, I'm not worried
about adding the RI and other necessities after the conversion.

Any input woudl be greatly appreciated...

--
Regards,
Jan Ferguson


Tim Young [Elevate Software] wrote:

> Al,
>
> << I'm sure you're sick of this question but do you have an updated
> timeframe for the release of v5?  No pressure, we're just trying to
> decide when to release our BDS2006 compiled app.  If it's coming out
> soon we'd like to release both upgrades at the same time.  Are we
> talking days, weeks, months?  Any hint would be helpful. >>
>
> I'd rather not say at this point.  It's getting closer every day, but
> I made the mistake of stating some estimates in the fall and now I've
> got egg on my face.  Basically, we sometimes have to go back and
> rewrite stuff if it isn't right (and we did in December), and so
> estimates aren't worth much once that happens.  I simply will not
> release the product until it is ready, so the release date will
> always suffer before the quality.
>
> I would basically plan your application around not having ElevateDB
> in the timeframe that you would wish.  That would be the safe and
> prudent course of action.

Tim

Al,

<< I think I speak for most of us that we'd
rather have a stable product released later than a buggier version
released sooner.  We love your stuff and we're looking forward to
seeing the new version when it's ready. >>

Hey, we've waited over 4 years for a Unicode-enabled version. Another month
or two is a breeze!

Seriously, your point is valid. I bet we'd all rather have a stable first release
than have a *quick* first release.

Regards,
Dan

Jan,

<< My question is, will it be fairly easy or difficult to convert DBIsam
v4.x tables to ElevateDB tables? If it would be like converting from
another database, then I might as well wait although the projects will take
a big hit on my goals and objectives this fiscal year. However, if
the base tables conversion is straight forward enough, I'm not worried about
adding the RI and other necessities after the conversion. >>

The base tables will convert over fine.  The issues that come into play are
the text index filtering, custom functions, server-side procedures, and
triggers.  They are all slightly different and will require some work to
convert.  However, the end result will be worth the effort, IMO.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

That's GREAT! That's all I need to know to get started. Thanks for the
insight.

--
Regards,
Jan Ferguson


Tim Young [Elevate Software] wrote:

> Jan,
>
> << My question is, will it be fairly easy or difficult to convert
> DBIsam v4.x tables to ElevateDB tables? If it would be like
> converting from another database, then I might as well wait although
> the projects will take a big hit on my goals and objectives this
> fiscal year. However, if the base tables conversion is straight
> forward enough, I'm not worried about adding the RI and other
> necessities after the conversion. >>
>
> The base tables will convert over fine.  The issues that come into
> play are the text index filtering, custom functions, server-side
> procedures, and triggers.  They are all slightly different and will
> require some work to convert.  However, the end result will be worth
> the effort, IMO.

Tim

Jan,

Something else you may need to consider is the component names, that will be
changing. I know for me personally, I will need to do a little more work, as
I have many custom procedures of my own that refer to TDBISAMTables /
Queries, that will need to have new units rewritten for TEDBTables (or
whatever).

Personally, I can't just do a simple search/replace as I will mostlikely
have some older program still running V4, whilst others running V5 when I
upgrade.

It's not a huge deal, but it is something worth considering if you have your
own custom units with procedures for DBISam, where you will require it to
remain the same for some applications, and changed for upgraded
applications.

If I'm missing something simple here - someone please step in.

Cheres

Adam.

Adam


I would say still little more than search and replace, just a bit more of it.

1. Copy the custom code & rename it
2. S&R for the ElevateDB stuff
3. S&R for your custom stuff

Roy Lambert

Roy,

> I would say still little more than search and replace, just a bit more of
it.

True. I sit corrected.  

Adam.