aagjohan@... (Aage Johansen) wrote in
news:4.3.2.7.2.20021009203629.00c01e78@127.0.0.1:

> Jeff Shoaf wrote:
> <<
> We currently have two IB 6.0 dialect 1 databases hosted on the same
> server that we're accessing using Paradox for Windows via the BDE and
> SQL Links. I'm getting ready to start a new project and I'd like to
> develop it using Firebird as well as converting the two existing
> databases to FB. All three would be running on the same server. We are
> committed to leaving the current applications and developing the new
> app in Paradox - yes, for valid reasons! The server will be running
> Windows 2000. ...
> >>
>
> Jeff, the BDE is dead (at least for C/S databases). This is Borland's
> position, and it was discussed at length in borland.public.bde earlier
> this year (July?).
>
> You say "for valid reasons". I say that this will most probably not
> be a success.
> There are now much better tools for writing a database app (and I used
> to love PDox and PAL!).
>
>
> Regards,
> Aage J.
>
>

There was quite a lot of discussion regarding Borland's position on the
BDE on the Paradox groups as well. Throw in Corel's current financial
position, and I agree that Paradox is in a perilous position. That's one
of the reason's I'm trying to migrate some of our stuff to C/S.

The valid reasons... When we started using Paradox, it was still a
vibrant Borland product. It wasn't a corporate standard, but the
corporate standard (Access - yuck!) didn't meet our needs. Over the
years, we've come to the point that we're using Paradox to run our
departments business - to the point that we hired an additional Paradox
programmer to provide backup.

Now I've ran into some things that Paradox alone can't handle, but
Paradox and a C/S database can. My fellow Paradox developers don't
believe that - they feel that if it can't be done in Paradox, we
shouldn't even be doing it! By migrating to a C/S backend, I'm trying to
ease into transitioning away from Paradox and if Paradox and/or the BDE
stop working due to OS changes, we'll be better prepared to change just
the front-end.

The company I work for is buying into MS's .Net stuff in a big way. We
are looking at moving to C# or VB.Net, but we have immediate needs that
can't wait for me to learn something else - I'm looking to have this app
up and running by mid-December. I can do that (well, without
documentation) using Paradox and IB, but not something else.