Delphi 7 to Delphi 2007

[Barry Dirks]

This is totally weird. I hope I can explain so it makes sense to somebody.

I have an application that contains about a million lines of code written
and compiled using Delphi 7. I bought Delphi 2007 several months ago and was
able to convert the app and all of the 3rd party controls fairly quickly.
I've released a version of the software and now I have 4 clients that are
seeing very strange behavior with TDBGrid. Here's what happens:

Launch the app and open a window that contains a TDBGrid component. If you
use any arrow key, home, end, pgup or pgdn the app appears to lock up. You
can't click on any menu item or button or close the app. But if you click on
the app icon on the start bar and click Close, you'll get the app's close
confirmation dialog that normally comes up when you click close in the app
itself. If you click No on app close dialog the app magically unlocks and
you can close the window, click menu items, etc. But if you try to navigate
the TDBGrid with the keyboard it'll "lockup" again.
Now, here's the kicker. If you run the same application, same code but
compiled with Delphi 7 on the same machine this doesn't happen. Plus, if you
run the D7-compiled app, then launch the D2007-compiled app the TDBGrid in
the D2007-compiled app works fine with the keyboard! Close the D7-compiled
app and the TDBGrid in the D2007-compiled app continues to work properly.
But close both apps and launch the D2007-compiled app and try to navigate a
TDBGrid with the keyboard and it locks up.

Does anyone have any clue what could be happening here? This doesn't happen
at every client site, nor does it happen here in our office.

Believe me, I've tried all kinds of things to try and determine what's
causing this including getting all the processes running on the clients'
machines and comparing them to machines in our office but nothing sticks
out.

Please HELP!!!

Thanks.

Barry Dirks
Jacksonville, FL

[Mike Orriss]

Barry Dirks wrote:

> Now, here's the kicker. If you run the same application, same code
> but compiled with Delphi 7 on the same machine this doesn't happen.
> Plus, if you run the D7-compiled app, then launch the D2007-compiled
> app the TDBGrid in the D2007-compiled app works fine with the
> keyboard! Close the D7-compiled app and the TDBGrid in the
> D2007-compiled app continues to work properly. But close both apps
> and launch the D2007-compiled app and try to navigate a TDBGrid with
> the keyboard and it locks up.
>
> Does anyone have any clue what could be happening here? This doesn't
> happen at every client site, nor does it happen here in our office.

Just a wild guess, but does it still happen if you disable anti-virus
software etc?

--
Mike

[Barry Dirks]

Good guess. Yes that helped at a couple of the client sites. But I still
have 2 clients that have turned off AV completely and it's still happening.

Even so, why would AV affect a D2007-compiled app and not a D7-compiled app?

"Mike Orriss" <m...@3kcc.co.uk> wrote in message
news:4864802b$1...@newsgroups.borland.com...

[MvT]

Hi All,

While we are on the topic of converting Delphi 7 - Delphi 2007...
I need assistance as well.

When opening my Delphi 7 project for the first time in Delphi 2007 it asked
me to convert it to VCL 32 application.
Everything went well and I then tried to compile the project.
Delphi 2007 gives me an compilation error message: "Class TADConnection not
found..."
I use a lot of ADO components in this project.

Why doesn't Delphi 2007 like ADO?
How to solve this problem?

Thanks

[Peter Below (TeamB)]

MvT wrote:

> Hi All,
>
> While we are on the topic of converting Delphi 7 - Delphi 2007...
> I need assistance as well.
>
> When opening my Delphi 7 project for the first time in Delphi 2007 it
> asked me to convert it to VCL 32 application. Everything went well
> and I then tried to compile the project. Delphi 2007 gives me an
> compilation error message: "Class TADConnection not found..." I use a
> lot of ADO components in this project.

Well, it is completely right since the class is named TADOConnection
<g>.

The class is defined in the ADODB unit and the unit name did not change
from D7. If you get this error when the IDE is trying to load a unit
containing a form or datamodule it may be due to the fact that the
correct design-time package (dclado100.bpl) is not loaded in the IDE.
Open the project. From the main menu use the Components->Install
package menu to call up the package dialog. Check whether you have the
"Codegear ADO DB components" package in the list and whether it is
checked.

Also call up the project options dialog and check all the pathes on the
conditionals/pathes tab for entries that may refer to D7 code units. Do
the same with the projects DPR file Uses clause, which also can contain
pathes.

--
Peter Below (TeamB)
Don't be a vampire (http://slash7.com/pages/vampires),
use the newsgroup archives :
http://www.tamaracka.com/search.htm
http://groups.google.com

[Benedictum]

Any reason why you want to convert it D2007? If it was working fine with D7
then don't fix it. I still have application written in D5 and I learned (the
hard way) that converting it with D2007 created more problem. My clients are
happy with the old D5-created app. I only use D2007 for new development
work.

Just my 2-bit experience.

"Barry Dirks" <ba...@tempus.com> wrote in message
news:48641643$1...@newsgroups.borland.com...

[Rob Uttley]

Barry, did you get a solution or explanation for this? Not that I have
a vested interest or anything, just I remember thinking this was one of
the more interesting issues to arise here recently, and as I convert a
lot of D7 code to D2007 it's something that might bite me later, too.

Cheers
Rob

--
Rob Uttley
www.robsoft.net