PowerCobol form all jumbled up

I have been programming in Fujitsu PowerCobol for 4 or 5 years.  Now
using V6.
I have a problem I've never seen before.  I program and run on
Windows PCs which are networked.

I have a form created in a project.  The form displays fine on my
development
machine just fine (Win2000).  It runs and displays fine on another
machine that uses
XP.  When I execute the program on another XP computer, the form
height/width are
changed, and all the controls on the form are in mixed up positions.
Fonts are all
mixed sizes.  Buttons are mixed sizes.  Just a mess.

On that same XP computer, all my other forms work and are used every
day,
so its not the runtime installation or the comptuter's hardware.

The affected form works fine on other PCs, not just this one, so it
would seem
the program itself is OK.

Sounds like some kind of compatibility bug, but I've never seen it
before.

HELP!

don

CarSalesman wrote:
>       I have been programming in Fujitsu PowerCobol for 4 or 5 years.
> Now using V6.
>       I have a problem I've never seen before.  I program and run on
>       Windows PCs which are networked.
>
>       I have a form created in a project.  The form displays fine on
> my development
>       machine just fine (Win2000).  It runs and displays fine on
> another machine that uses
>       XP.  When I execute the program on another XP computer, the form
> height/width are
>       changed, and all the controls on the form are in mixed up
> positions. Fonts are all
>       mixed sizes.  Buttons are mixed sizes.  Just a mess.
>
>       On that same XP computer, all my other forms work and are used
> every day,
>       so its not the runtime installation or the comptuter's hardware.
>
>       The affected form works fine on other PCs, not just this one,
> so it would seem
>       the program itself is OK.
>
>       Sounds like some kind of compatibility bug, but I've never seen
> it before.
>
>       HELP!

Wow! Never seen anything like that!

Looks like you'll have to employ standard hit-and-miss debugging techniques
(disable parts of the form until you find the culprit, etc.)

You should also post a query on (msnews.microsoft.com /
microsoft.public.windowsxp.general) newsgroup along the lines of "same
program on one XP machine looks ghastly..." The folk over there are experts
in pointing out obscure registry entries, conflicting drivers and options,
and so forth.

Please report back what you find.

"JerryMouse" <nospam@bisusa.com> wrote in message news:<7IqdnfWwatVXFXPdRVn-jg@giganews.com
>...
> CarSalesman wrote: 
>
> Wow! Never seen anything like that!
>
> Looks like you'll have to employ standard hit-and-miss debugging technique
s
> (disable parts of the form until you find the culprit, etc.)
>
> You should also post a query on (msnews.microsoft.com /
> microsoft.public.windowsxp.general) newsgroup along the lines of "same
> program on one XP machine looks ghastly..." The folk over there are expert
s
> in pointing out obscure registry entries, conflicting drivers and options,
> and so forth.
>
> Please report back what you find.


Does the affected machine have a default printer defined?

Jeff Campbell
n8wxs@arrl.net