 |
BorlandTalk.com Borland discussion newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
Google Mike Guest
|
Posted: Mon Sep 22, 2003 8:15 pm Post subject: Migrating from Delphi 3 Cli/Srv to Delphi Studio 7 |
|
|
We're having some interesting discoveries with Delphi 3 Cli/Srv. If
you connect to SQL 6.5 to 7, you can use the built-in BDE driver and
read/write tables and execute stored procs. But you can't connect to
SQL 2K. Here's what happens. With SQL 2K, the BDE driver can see only
the tables and not the stored procedures. With the ODBC driver via
Delphi 3, however, you can execute the stored procedures but not
read/write the tables. So, the end result was that we had to use both
ODBC and BDE connections to the SQL 2K database.
My supervisor said we have some problems rolling out ODBC control
panel to a bunch of cheap, low memory workstations, so he isn't liking
this solution. He's wondering whether it would be better to migrate
from Delphi 3 to Delphi 7 and stick purely with the BDE drivers.
Note also we're using a bunch of data controls from InfoPower and
Delphi 3.
We have 5 client/server database apps to convert in less than 2
months. Total, that's 144,311 lines of code. I'm only one developer
and only have Delphi 3 experience, but have a lot of VB/ASP and
Java/JSP experience. I can hire another contract developer if need be
to get through this.
My beliefs, however, are that:
(a) If we're going to migrate, why not migrate to VB6 because then we
can get through future upgrades faster and use people out of college.
Delphi programmers are hard to come by.
(b) I've done VB migrations, and heard of many others, moving from VB3
or VB4 to VB6, and they were somewhat unpleasant because either (a)
sometimes there was no control upgrade path and something had to be
rewritten with a completely different control, or (b) sometimes the
object model for a control was completely different. I feel that
moving from Delphi 3 to Delphi 7 might have the same kind of
nightmares to mull through.
What's your take on this? Help me give my supervisor a clue as to what
we might expect, good or bad.
|
|
| Back to top |
|
 |
Jay Guest
|
Posted: Thu Oct 16, 2003 1:28 pm Post subject: Re: Migrating from Delphi 3 Cli/Srv to Delphi Studio 7 |
|
|
Moving a Delphi application to VB is not at all a good idea when you
consider the performance. I see that your application was developed in
Delphi 3. Starting from Delphi 5 the Borland has made it very stable
with a lot of added features. Since your database is SQL 2000 the best
way to go is to migrate to DElphi 7 and use ADO datasets instead of
BDE. The application will become standalone and is faster. When it
comes to new features each new version of Delphi comes with a lot of
new components , but the skeleton/ architecture of Delphi has never
changed ( I mean all the underlying classes). So it won't be a big
issue if you have good Delphi programmers who are ready to migrate the
tool
[email]googlemike (AT) hotpop (DOT) com[/email] (Google Mike) wrote in message news:<25d8d6a8.0309221215.4c96787b (AT) posting (DOT) google.com>...
| Quote: | We're having some interesting discoveries with Delphi 3 Cli/Srv. If
you connect to SQL 6.5 to 7, you can use the built-in BDE driver and
read/write tables and execute stored procs. But you can't connect to
SQL 2K. Here's what happens. With SQL 2K, the BDE driver can see only
the tables and not the stored procedures. With the ODBC driver via
Delphi 3, however, you can execute the stored procedures but not
read/write the tables. So, the end result was that we had to use both
ODBC and BDE connections to the SQL 2K database.
My supervisor said we have some problems rolling out ODBC control
panel to a bunch of cheap, low memory workstations, so he isn't liking
this solution. He's wondering whether it would be better to migrate
from Delphi 3 to Delphi 7 and stick purely with the BDE drivers.
Note also we're using a bunch of data controls from InfoPower and
Delphi 3.
We have 5 client/server database apps to convert in less than 2
months. Total, that's 144,311 lines of code. I'm only one developer
and only have Delphi 3 experience, but have a lot of VB/ASP and
Java/JSP experience. I can hire another contract developer if need be
to get through this.
My beliefs, however, are that:
(a) If we're going to migrate, why not migrate to VB6 because then we
can get through future upgrades faster and use people out of college.
Delphi programmers are hard to come by.
(b) I've done VB migrations, and heard of many others, moving from VB3
or VB4 to VB6, and they were somewhat unpleasant because either (a)
sometimes there was no control upgrade path and something had to be
rewritten with a completely different control, or (b) sometimes the
object model for a control was completely different. I feel that
moving from Delphi 3 to Delphi 7 might have the same kind of
nightmares to mull through.
What's your take on this? Help me give my supervisor a clue as to what
we might expect, good or bad.
|
|
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|