Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Corrupted form?

2 posts in PB Infomaker Report Writer Last posting was on 1997-10-23 02:13:45.0Z
Sheila C. Conant Posted on 1997-10-22 21:53:19.0Z
Newsgroups: sybase.public.infomaker.general
Date: Wed, 22 Oct 1997 17:53:19 -0400
From: "Sheila C. Conant" <SConant@worldnet.att.net>
Reply-To: SConant@worldnet.att.net
Organization: Conant & Associates, Inc.
X-Mailer: Mozilla 3.0 (Win95; U)
MIME-Version: 1.0
Subject: Corrupted form?
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 33
Message-ID: <348_344E75CF.AF2@worldnet.att.net>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.infomaker.general:7416
Article PK: 244471

I'm having many strange problems with IM.

I have a form that references a single table with most of the fields
using a dropdown datawindow as the EDIT type. I created new dddw's and
changed each field's reference to use the new dddw's. At some point,
(this is the second time it has happened) the form is corrupted in these
ways:

1. When I show the properties dialog, all tab labels are missing EXCEPT
for the Font label
2. When I try to make a change to any field on the form, it won't save
the change
3. Sometimes when I try to look at the SQL for the form, it tells me
that the table doesn't exist (and it does)
4. When I try to close the form I get a messagebox with the message
'Message xxxx can't be found'
5. Sometimes when I open the form I can click on the form controls
directly, other times I click and get the whole datawindow and can't
access the form controls.

I made changes to this form using PB 5.0.02 when I've been prevented
from doing so in IM. I am running IM 5.0.02 connected to SQL Server 6.5
using the native driver.

Other forms in the pbl don't have these problems.

I really do not want to rebuild this window again - does anyone know
what may have caused these problems and more importantly, how to make
things right?


Stephen Dupre[Powersoft Tools, Sybase Inc.] Posted on 1997-10-23 02:13:45.0Z
Newsgroups: sybase.public.infomaker.general
Date: Wed, 22 Oct 1997 22:13:45 -0400
From: "Stephen Dupre[Powersoft Tools, Sybase Inc.]" <sdupre@powersoft.com>
Reply-To: sdupre@powersoft.com
Organization: Powersoft Tools
X-Mailer: Mozilla 3.0Gold (WinNT; U)
MIME-Version: 1.0
Subject: Re: Corrupted form?
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 57
Message-ID: <348_344EB2D9.4ACD@powersoft.com>
References: <348_344E75CF.AF2@worldnet.att.net>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.infomaker.general:7415
Article PK: 244470


Sheila C. Conant wrote:
>
> I'm having many strange problems with IM.
>
> I have a form that references a single table with most of the fields
> using a dropdown datawindow as the EDIT type. I created new dddw's and
> changed each field's reference to use the new dddw's. At some point,
> (this is the second time it has happened) the form is corrupted in these
> ways:
>
> 1. When I show the properties dialog, all tab labels are missing EXCEPT
> for the Font label
> 2. When I try to make a change to any field on the form, it won't save
> the change
> 3. Sometimes when I try to look at the SQL for the form, it tells me
> that the table doesn't exist (and it does)
> 4. When I try to close the form I get a messagebox with the message
> 'Message xxxx can't be found'
> 5. Sometimes when I open the form I can click on the form controls
> directly, other times I click and get the whole datawindow and can't
> access the form controls.
>
> I made changes to this form using PB 5.0.02 when I've been prevented
> from doing so in IM. I am running IM 5.0.02 connected to SQL Server 6.5
> using the native driver.
>
> Other forms in the pbl don't have these problems.
>
> I really do not want to rebuild this window again - does anyone know
> what may have caused these problems and more importantly, how to make
> things right?

The part where the "table does not exist" might be because of the
prefixing or lack of prefixing in the 'Update Characteristics' dialog.

If a non-owner of the table(s) created the form, you might see

"dbo.employee"

as the "table to update". We had one bug where modifying the report
would strip out the 'dbo' and corrupt the form somewhat.

If the form is not updateable ("Allow updates" off in Update
Characteristics), you can still have some underlying garbage saved
internally which you've probably fixed in PB (PB correctly shows you the
"garbage").

I would start with the prefixing first (ie who you're logged on as when
creating both the form and the dddws for the form) and go from there.
If you have Powerbuilder, keep it running at the same time so you can
query the <form>@1 or <form>@2 datawindows created for the form.

Stephen Dupre
Powersoft Tools