Hi,

We are finally trying to plan a port from DBISAM 3 in our busy development
schedule.  My first question is should I be porting to DBISAM V4 or
ElevateDB?  Both are going to require full bug testing as there are quite a
few SQL-based changes in application and reports.  So I am trying to
ascertain whether I in fact need to move to ElevateDB.  If I am to move to
ElevateDB then I really don't want to go to DBISAM4 first as an interim as
there is a lot of testing as mentioned.

I have been reading a few queries here on the newsgroups and there seems
that there are still a few bugs that need to be addressed.  So for those who
have been through the process already, is it worthwhile moving to ElevateDB?
Is there alot more work to move to ElevateDB than DBISAM4?  And is DBISAM
still going to be supported or will it be phased out from a long-term
perspective?

So many questions.

TIA

Alex

Alex,

Personally, I would suggest just forging ahead to ElevateDB.  Yes, there
are little things that have come up, but Tim has responded quickly
addressing
them.  EDB really provides a nice foundation and V2 is closing in on
release.

My personal transition from DBISAM4 to EDB was relatively painless.  There
was a small learning curver to deal with catalogs, but in the long run, more
beneficial, I think.

My own take is that the majority of new "goodies" will be with ElevateDB,
which is
the present and future.  DBISAM was the past.  Prior to the support plan,
Tim
had essentially given DBISAM another year, but only for bug support.  Now
with the new support plan, that will help dictate how much further DBISAM
goes,
in terms of adding a few requests for DBISAM 4.x that are doable, even to a
point of supporting Delphi 2008, however I personally doubt a DBISAM 5.x
will
be released, nor is there really a need (IMHO).

Lance


"DBISAM" <nooone@noonoe.com> wrote in message
news:DBC16B51-E9E2-49C0-B1AC-687FD5004E52@news.elevatesoft.com...
> Hi,
>
> We are finally trying to plan a port from DBISAM 3 in our busy development
> schedule.  My first question is should I be porting to DBISAM V4 or
> ElevateDB?  Both are going to require full bug testing as there are quite
> a few SQL-based changes in application and reports.  So I am trying to
> ascertain whether I in fact need to move to ElevateDB.  If I am to move to
> ElevateDB then I really don't want to go to DBISAM4 first as an interim as
> there is a lot of testing as mentioned.
>
> I have been reading a few queries here on the newsgroups and there seems
> that there are still a few bugs that need to be addressed.  So for those
> who have been through the process already, is it worthwhile moving to
> ElevateDB? Is there alot more work to move to ElevateDB than DBISAM4?  And
> is DBISAM still going to be supported or will it be phased out from a
> long-term perspective?
>
> So many questions.
>
> TIA
>
> Alex

Hi,

Conversion from DBISAM 3 to ElevateDB will take a little longer than
converting to DBISAM 4, however, there are some significant performance and
language improvements that make it worth the effort. IMO whilst DBISAM 4
support will continue for some time, we are unlikely to see any new
features/performance enhancements introduced. My opinion is to go with
ElevateDB.
--

Best Regards

Steve
[Team Elevate]

"DBISAM" <nooone@noonoe.com> wrote in message
news:DBC16B51-E9E2-49C0-B1AC-687FD5004E52@news.elevatesoft.com...
> Hi,
>
> We are finally trying to plan a port from DBISAM 3 in our busy development
> schedule.  My first question is should I be porting to DBISAM V4 or
> ElevateDB?  Both are going to require full bug testing as there are quite
> a few SQL-based changes in application and reports.  So I am trying to
> ascertain whether I in fact need to move to ElevateDB.  If I am to move to
> ElevateDB then I really don't want to go to DBISAM4 first as an interim as
> there is a lot of testing as mentioned.
>
> I have been reading a few queries here on the newsgroups and there seems
> that there are still a few bugs that need to be addressed.  So for those
> who have been through the process already, is it worthwhile moving to
> ElevateDB? Is there alot more work to move to ElevateDB than DBISAM4?  And
> is DBISAM still going to be supported or will it be phased out from a
> long-term perspective?
>
> So many questions.
>
> TIA
>
> Alex

Two words:  STORED PROCEDURES!  (OK, DBISAM has "accessible Delphi
library functions" that were called stored procedure, but not really
SQL stored in the database that can be changed without recompiling and
redeploying the server!)

Everyone has their favorite feature and mine is that.  Yeah, there's a
paradigm shift when moving to new syntax and ways of doing things, but
the end result will pay off.  I'm always in favor of moving to the
latest technology.  And since it moves so fast anyway, why move to
something that is already slated for obsolescence?

--
David Cornelius
CorneliusConcepts.com
custom designed software


DBISAM wrote:

> Hi,
>
> We are finally trying to plan a port from DBISAM 3 in our busy
> development schedule.  My first question is should I be porting to
> DBISAM V4 or ElevateDB?  Both are going to require full bug testing
> as there are quite a few SQL-based changes in application and
> reports.  So I am trying to ascertain whether I in fact need to move
> to ElevateDB.  If I am to move to ElevateDB then I really don't want
> to go to DBISAM4 first as an interim as there is a lot of testing as
> mentioned.
>
> I have been reading a few queries here on the newsgroups and there
> seems that there are still a few bugs that need to be addressed.  So
> for those who have been through the process already, is it worthwhile
> moving to ElevateDB? Is there alot more work to move to ElevateDB
> than DBISAM4?  And is DBISAM still going to be supported or will it
> be phased out from a long-term perspective?
>
> So many questions.
>
> TIA
>
> Alex

Alex

>is it worthwhile moving to ElevateDB?

Yes - but I'd wait for V2, it should have some additions to make the port easier

>Is there a lot more work to move to ElevateDB than DBISAM4?

Yes - just search for posts with my name and you'll get a good sample of the problems.

>And is DBISAM
>still going to be supported or will it be phased out from a long-term
>perspective?

Still going to be around.

Roy Lambert [Team Elevate]

Alex,

<< I have been reading a few queries here on the newsgroups and there seems
that there are still a few bugs that need to be addressed. >>

Just a quick clarification - the bugs that are cropping up now are almost
entirely relegated to features that aren't in DBISAM 3 anyways, so you
wouldn't be using them in your application.  ElevateDB started out in
version 1.00 being tested with the same framework as DBISAM 4, so there is a
baseline quality standard that we have maintained for DBISAM customers from
day one.

--
Tim Young
Elevate Software
www.elevatesoft.com

Alex,

Roy, Steve and others have given you good reason and information on ElevateDb conversions and I can only add my own experiences and
support towards your wanting to convert to ElevateDB. I have fully converted one smaller C/S application from DBISAM v4.xx to ElevateDB and it
was absolutely painless. I didn't have any SQL statements or procedures so it was a very simple conversion but absolutely painless.

I am currently converting a much larger C/S application, again from DBISAM v4.xx to ElevateDB v1 and haven't experienced any major issues
yet. I am kind of going slow on this conversion as I am waiting for ElevateDB v2 to be released to include functionality that version 2 will include. I
don't expect any issues. Luckily, like Roy Lambert, I never used a lot of SQL in previous applications so that has helped my conversion
experience. Since I did convert from DBISAM v4 versus you converting from version 3, I cannot help you in that regard. I can say that when I
converted my apps (the same ones I am now converting to ElevateDB) from DBISAM version 3 to version 4, I had no issues either.

Converting to ElevateDB is the right thing to do, IMHO. I have noticed an increase in speed and the stability has been as good as with DBISAM in
the one fully converted app I spoke of earlier. I can see any reason why you shouldn't convert within your own timeframe. You know that the
support from Tim will be great as always. It's a winning combination.

Regards,
Jan Ferguson [Team Elevate]


"DBISAM" <nooone@noonoe.com> wrote:

If I am to move to
ElevateDB then I really don't want to go to DBISAM4 first as an interim as
there is a lot of testing as mentioned.

I have been reading a few queries here on the newsgroups and there seems
that there are still a few bugs that need to be addressed.  So for those who
have been through the process already, is it worthwhile moving to ElevateDB?
Is there alot more work to move to ElevateDB than DBISAM4?  And is DBISAM
still going to be supported or will it be phased out from a long-term
perspective?