 |
BorlandTalk.com
Borland discussion newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
Shel
Guest
|
 Posted: Thu Sep 22, 2005 4:21 pm Post subject: Delphi 3 Problem in Win XP |
 |
|
I have a financial program that I wrote several years ago using Delphi
3. It has been working well under Windows 98.
I now have a new computer that uses Windows XP. One of the program's
components, PosLongintEdit, is derived from TEdit. But when I try to
enter a value in the field, nothing appears on the screen and the
Edit's text parameter remains empty.
Any suggestions on what the problem might be (and how to fix it) will
be appreciated.
|
|
| Back to top |
|
 |
John P
Guest
|
| Posted: Fri Sep 23, 2005 10:34 am Post subject: Re: Delphi 3 Problem in Win XP |
|
|
Shel wrote:
| Quote: |
One of the program's
components, PosLongintEdit, is derived from TEdit. But when I try to
enter a value in the field, nothing appears on the screen and the
Edit's text parameter remains empty.
|
Does that mean that you have no problems with standard TEdit controls
and XP?
| Quote: | Any suggestions on what the problem might be (and how to fix it) will
be appreciated.
|
I have never hear about PosLongintEdit control. But when it is built
arount TEdit, I would not suppose that there is tons of difficult VCL
code to read in the PosLongintEdit control's source.
Debugging under WinXP should quite easily point you where something goes
wrong, and why you loose your text values.
John P
|
|
| Back to top |
|
|
Laurie Boshell
Guest
|
| Posted: Sat Sep 24, 2005 3:27 am Post subject: Re: Delphi 3 Problem in Win XP |
|
|
"John P" <john.p (AT) spam (DOT) mimidi.se> wrote
| Quote: | Shel wrote:
One of the program's
components, PosLongintEdit, is derived from TEdit. But when I try to
enter a value in the field, nothing appears on the screen and the
Edit's text parameter remains empty.
Does that mean that you have no problems with standard TEdit controls
and XP?
Any suggestions on what the problem might be (and how to fix it) will
be appreciated.
I have never hear about PosLongintEdit control. But when it is built
arount TEdit, I would not suppose that there is tons of difficult VCL
code to read in the PosLongintEdit control's source.
Debugging under WinXP should quite easily point you where something goes
wrong, and why you loose your text values.
John P
I use D3 under XP extensively. Apart from a patch for the way D3 deals with |
printers, I've had no problems with a large medical billing and graphics
system.
I'm using components derived from TEdit with no problems.
Can you isolate the code? I'd be happy to look at it.
Laurie.
|
|
| 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
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
