Opening a datawindow crashes PowerBuilder

At work we have about 5 different developers that experienced a problem when
opening any datawindow from the PowerBuilder painter.  PB crashes and halts
altogether.

Funny thing is their PowerBuilder was working fine the day before.  My
PowerBuilder still is working fine and some other developers have not
experienced the problem.  All of the affected PowerBuilder programs are on
separate pc's and the developers work on different PowerBuilder projects.
That makes the mystery even more confusing.

The error is a pb70.exe - "Application Error" with the error being "The
instruction at "0x77fca2bf" referenced memory at "0x8328d40f".  The memory
could not be "written"."

Any help in resolving this is greatly appreciated.  All of our efforts of
reinstalling PB to installing the 03 patch have failed.  You can't even
create a brand new project and then a new datawindow without it crashing.

Thanks,

Warren


0
Warren
1/29/2002 8:15:25 PM
sybase.powerbuilder.general 62418 articles. 17 followers. Follow

15 Replies
733 Views

Similar Articles

[PageSpeed] 43

It's probably caused due to inconsistent data written to the
"HKEY_CURRENT_USER" registry key for this users. I already experienced a
similar problem in Windows 2000. Find the
HKEY_CURRENT_USER\Software\Sybase\PowerBuilder key in the registry and
delete it, or recreate the user profile for the affected users.

Remember, that I'm not offering any sure about it working, and that changing
values in the registry can damage persistently your machine. ;)

HTH,

Wendell Rios.

"Warren R" <warren_reinke@concentra.com> wrote in message
news:DULohJQqBHA.52@forums.sybase.com...
> At work we have about 5 different developers that experienced a problem
when
> opening any datawindow from the PowerBuilder painter.  PB crashes and
halts
> altogether.
>
> Funny thing is their PowerBuilder was working fine the day before.  My
> PowerBuilder still is working fine and some other developers have not
> experienced the problem.  All of the affected PowerBuilder programs are on
> separate pc's and the developers work on different PowerBuilder projects.
> That makes the mystery even more confusing.
>
> The error is a pb70.exe - "Application Error" with the error being "The
> instruction at "0x77fca2bf" referenced memory at "0x8328d40f".  The memory
> could not be "written"."
>
> Any help in resolving this is greatly appreciated.  All of our efforts of
> reinstalling PB to installing the 03 patch have failed.  You can't even
> create a brand new project and then a new datawindow without it crashing.
>
> Thanks,
>
> Warren
>
>


0
Wendell
1/29/2002 8:11:56 PM
Delete the key
HKCU\Software\Sybase\PowerBuilder\7.0\Layout\Default\Datawindow

--

Simon Caldwell
Get Real Systems Ltd
Holtby Manor, Stamford Bridge Road, York, YO19 5LL
Tel +44 (0)1904 481999 Fax +44 (0)1904 481666
Visit us at www.getrealsystems.com
Procurement Control Specialists
Controlling corporate spend and streamlining procurement processes


"Warren R" <warren_reinke@concentra.com> wrote in message
news:DULohJQqBHA.52@forums.sybase.com...
> At work we have about 5 different developers that experienced a problem
when
> opening any datawindow from the PowerBuilder painter.  PB crashes and
halts
> altogether.
>
> Funny thing is their PowerBuilder was working fine the day before.  My
> PowerBuilder still is working fine and some other developers have not
> experienced the problem.  All of the affected PowerBuilder programs are on
> separate pc's and the developers work on different PowerBuilder projects.
> That makes the mystery even more confusing.
>
> The error is a pb70.exe - "Application Error" with the error being "The
> instruction at "0x77fca2bf" referenced memory at "0x8328d40f".  The memory
> could not be "written"."
>
> Any help in resolving this is greatly appreciated.  All of our efforts of
> reinstalling PB to installing the 03 patch have failed.  You can't even
> create a brand new project and then a new datawindow without it crashing.
>
> Thanks,
>
> Warren
>
>


0
Simon
1/30/2002 9:52:53 AM
We've tried both suggestions.  Deletion of the
HKEY_CURRENT_USER\Software\Sybase\PowerBuilder\7.0\Layout\Default\Datawindow
and the entire PowerBuilder key.  None of which has worked.  We still cannot
open any datawindows within the affected PowerBuilder programs.  Thanks for
your suggestions though.

-- Warren


"Wendell Rios" <walmeida@tecnotrends.com.br> wrote in message
news:mUx84MQqBHA.286@forums.sybase.com...
> It's probably caused due to inconsistent data written to the
> "HKEY_CURRENT_USER" registry key for this users. I already experienced a
> similar problem in Windows 2000. Find the
> HKEY_CURRENT_USER\Software\Sybase\PowerBuilder key in the registry and
> delete it, or recreate the user profile for the affected users.
>
> Remember, that I'm not offering any sure about it working, and that
changing
> values in the registry can damage persistently your machine. ;)
>
> HTH,
>
> Wendell Rios.
>
> "Warren R" <warren_reinke@concentra.com> wrote in message
> news:DULohJQqBHA.52@forums.sybase.com...
> > At work we have about 5 different developers that experienced a problem
> when
> > opening any datawindow from the PowerBuilder painter.  PB crashes and
> halts
> > altogether.
> >
> > Funny thing is their PowerBuilder was working fine the day before.  My
> > PowerBuilder still is working fine and some other developers have not
> > experienced the problem.  All of the affected PowerBuilder programs are
on
> > separate pc's and the developers work on different PowerBuilder
projects.
> > That makes the mystery even more confusing.
> >
> > The error is a pb70.exe - "Application Error" with the error being "The
> > instruction at "0x77fca2bf" referenced memory at "0x8328d40f".  The
memory
> > could not be "written"."
> >
> > Any help in resolving this is greatly appreciated.  All of our efforts
of
> > reinstalling PB to installing the 03 patch have failed.  You can't even
> > create a brand new project and then a new datawindow without it
crashing.
> >
> > Thanks,
> >
> > Warren
> >
> >
>
>


0
Warren
1/30/2002 1:39:03 PM
We now have submitted our issue to Sybase.  Unfortunately our company
decided not to renew our maintenance subscription with them so we'll have to
rely on them reading our posted issue.  Could be of thousands others.

Warren

"Warren R" <warren_reinke@concentra.com> wrote in message
news:DULohJQqBHA.52@forums.sybase.com...
> At work we have about 5 different developers that experienced a problem
when
> opening any datawindow from the PowerBuilder painter.  PB crashes and
halts
> altogether.
>
> Funny thing is their PowerBuilder was working fine the day before.  My
> PowerBuilder still is working fine and some other developers have not
> experienced the problem.  All of the affected PowerBuilder programs are on
> separate pc's and the developers work on different PowerBuilder projects.
> That makes the mystery even more confusing.
>
> The error is a pb70.exe - "Application Error" with the error being "The
> instruction at "0x77fca2bf" referenced memory at "0x8328d40f".  The memory
> could not be "written"."
>
> Any help in resolving this is greatly appreciated.  All of our efforts of
> reinstalling PB to installing the 03 patch have failed.  You can't even
> create a brand new project and then a new datawindow without it crashing.
>
> Thanks,
>
> Warren
>
>


0
Warren
1/30/2002 1:54:24 PM
Have you exported the syntax and looked at? From my experience PB crashes in
this circumstances when there are some complex fields (groups for examples)
and/or a "wrong" connection is active (to a different DB etc), or even
worse... some field get mess inside.

Andy N.


"Warren R" <warren_reinke@concentra.com> ha scritto nel messaggio
news:DULohJQqBHA.52@forums.sybase.com...
> At work we have about 5 different developers that experienced a problem
when
> opening any datawindow from the PowerBuilder painter.  PB crashes and
halts
> altogether.
>
> Funny thing is their PowerBuilder was working fine the day before.  My
> PowerBuilder still is working fine and some other developers have not
> experienced the problem.  All of the affected PowerBuilder programs are on
> separate pc's and the developers work on different PowerBuilder projects.
> That makes the mystery even more confusing.
>
> The error is a pb70.exe - "Application Error" with the error being "The
> instruction at "0x77fca2bf" referenced memory at "0x8328d40f".  The memory
> could not be "written"."
>
> Any help in resolving this is greatly appreciated.  All of our efforts of
> reinstalling PB to installing the 03 patch have failed.  You can't even
> create a brand new project and then a new datawindow without it crashing.
>
> Thanks,
>
> Warren
>
>

0
Andy
1/30/2002 2:31:11 PM
Can you create a new datawindow in this computers?

"Warren R" <warren_reinke@concentra.com> wrote in message
news:ekqjsQZqBHA.286@forums.sybase.com...
> We've tried both suggestions.  Deletion of the
>
HKEY_CURRENT_USER\Software\Sybase\PowerBuilder\7.0\Layout\Default\Datawindow
> and the entire PowerBuilder key.  None of which has worked.  We still
cannot
> open any datawindows within the affected PowerBuilder programs.  Thanks
for
> your suggestions though.
>
> -- Warren
>
>
> "Wendell Rios" <walmeida@tecnotrends.com.br> wrote in message
> news:mUx84MQqBHA.286@forums.sybase.com...
> > It's probably caused due to inconsistent data written to the
> > "HKEY_CURRENT_USER" registry key for this users. I already experienced a
> > similar problem in Windows 2000. Find the
> > HKEY_CURRENT_USER\Software\Sybase\PowerBuilder key in the registry and
> > delete it, or recreate the user profile for the affected users.
> >
> > Remember, that I'm not offering any sure about it working, and that
> changing
> > values in the registry can damage persistently your machine. ;)
> >
> > HTH,
> >
> > Wendell Rios.
> >
> > "Warren R" <warren_reinke@concentra.com> wrote in message
> > news:DULohJQqBHA.52@forums.sybase.com...
> > > At work we have about 5 different developers that experienced a
problem
> > when
> > > opening any datawindow from the PowerBuilder painter.  PB crashes and
> > halts
> > > altogether.
> > >
> > > Funny thing is their PowerBuilder was working fine the day before.  My
> > > PowerBuilder still is working fine and some other developers have not
> > > experienced the problem.  All of the affected PowerBuilder programs
are
> on
> > > separate pc's and the developers work on different PowerBuilder
> projects.
> > > That makes the mystery even more confusing.
> > >
> > > The error is a pb70.exe - "Application Error" with the error being
"The
> > > instruction at "0x77fca2bf" referenced memory at "0x8328d40f".  The
> memory
> > > could not be "written"."
> > >
> > > Any help in resolving this is greatly appreciated.  All of our efforts
> of
> > > reinstalling PB to installing the 03 patch have failed.  You can't
even
> > > create a brand new project and then a new datawindow without it
> crashing.
> > >
> > > Thanks,
> > >
> > > Warren
> > >
> > >
> >
> >
>
>


0
Wendell
1/30/2002 8:08:59 PM
This just started happening for all datawindows in several different
projects for only some PCs.  Yet opening the same exact datawindow from my
PC works fine.  Weird, uh!


"Andy Neagu" <andy_neagu@hotmail.com> wrote in message
news:mpS8ivZqBHA.185@forums.sybase.com...
> Have you exported the syntax and looked at? From my experience PB crashes
in
> this circumstances when there are some complex fields (groups for
examples)
> and/or a "wrong" connection is active (to a different DB etc), or even
> worse... some field get mess inside.
>
> Andy N.
>
>
> "Warren R" <warren_reinke@concentra.com> ha scritto nel messaggio
> news:DULohJQqBHA.52@forums.sybase.com...
> > At work we have about 5 different developers that experienced a problem
> when
> > opening any datawindow from the PowerBuilder painter.  PB crashes and
> halts
> > altogether.
> >
> > Funny thing is their PowerBuilder was working fine the day before.  My
> > PowerBuilder still is working fine and some other developers have not
> > experienced the problem.  All of the affected PowerBuilder programs are
on
> > separate pc's and the developers work on different PowerBuilder
projects.
> > That makes the mystery even more confusing.
> >
> > The error is a pb70.exe - "Application Error" with the error being "The
> > instruction at "0x77fca2bf" referenced memory at "0x8328d40f".  The
memory
> > could not be "written"."
> >
> > Any help in resolving this is greatly appreciated.  All of our efforts
of
> > reinstalling PB to installing the 03 patch have failed.  You can't even
> > create a brand new project and then a new datawindow without it
crashing.
> >
> > Thanks,
> >
> > Warren
> >
> >
>


0
Warren
1/30/2002 8:14:40 PM
We have this same problem..Removing the registry entry for the 
datawindow was unsuccessful.  

On Wed, 30 Jan 2002 09:52:53 -0000,
 in powersoft.public.powerbuilder.general
Simon Caldwell [TeamSybase] <simonDOTcaldwellATgetrealsystemsDOTcom> wrote: 
>Delete the key
>HKCU\Software\Sybase\PowerBuilder\7.0\Layout\Default\Datawindow
>
>--
>
>Simon Caldwell
>Get Real Systems Ltd
>Holtby Manor, Stamford Bridge Road, York, YO19 5LL
>Tel +44 (0)1904 481999 Fax +44 (0)1904 481666
>Visit us at www.getrealsystems.com
>Procurement Control Specialists
>Controlling corporate spend and streamlining procurement processes
>
>
>"Warren R" <warren_reinke@concentra.com> wrote in message
>news:DULohJQqBHA.52@forums.sybase.com...
>> At work we have about 5 different developers that experienced a problem
>when
>> opening any datawindow from the PowerBuilder painter.  PB crashes and
>halts
>> altogether.
>>
>> Funny thing is their PowerBuilder was working fine the day before.  My
>> PowerBuilder still is working fine and some other developers have not
>> experienced the problem.  All of the affected PowerBuilder programs are on
>> separate pc's and the developers work on different PowerBuilder projects.
>> That makes the mystery even more confusing.
>>
>> The error is a pb70.exe - "Application Error" with the error being "The
>> instruction at "0x77fca2bf" referenced memory at "0x8328d40f".  The memory
>> could not be "written"."
>>
>> Any help in resolving this is greatly appreciated.  All of our efforts of
>> reinstalling PB to installing the 03 patch have failed.  You can't even
>> create a brand new project and then a new datawindow without it crashing.
>>
>> Thanks,
>>
>> Warren
>>
>>
>
>

---== Posted via the PFCGuide Web Newsreader ==---
http://www.pfcguide.com/_newsgroups/group_list.asp
0
Carlos
1/30/2002 8:34:45 PM
Check for multiple copies of your PB DLL's. If you have several copies, make
sure they're all the same version.

"Warren R" <warren_reinke@concentra.com> wrote in message
news:KuhdxtcqBHA.204@forums.sybase.com...
> This just started happening for all datawindows in several different
> projects for only some PCs.  Yet opening the same exact datawindow from my
> PC works fine.  Weird, uh!
>
>
> "Andy Neagu" <andy_neagu@hotmail.com> wrote in message
> news:mpS8ivZqBHA.185@forums.sybase.com...
> > Have you exported the syntax and looked at? From my experience PB
crashes
> in
> > this circumstances when there are some complex fields (groups for
> examples)
> > and/or a "wrong" connection is active (to a different DB etc), or even
> > worse... some field get mess inside.
> >
> > Andy N.
> >
> >
> > "Warren R" <warren_reinke@concentra.com> ha scritto nel messaggio
> > news:DULohJQqBHA.52@forums.sybase.com...
> > > At work we have about 5 different developers that experienced a
problem
> > when
> > > opening any datawindow from the PowerBuilder painter.  PB crashes and
> > halts
> > > altogether.
> > >
> > > Funny thing is their PowerBuilder was working fine the day before.  My
> > > PowerBuilder still is working fine and some other developers have not
> > > experienced the problem.  All of the affected PowerBuilder programs
are
> on
> > > separate pc's and the developers work on different PowerBuilder
> projects.
> > > That makes the mystery even more confusing.
> > >
> > > The error is a pb70.exe - "Application Error" with the error being
"The
> > > instruction at "0x77fca2bf" referenced memory at "0x8328d40f".  The
> memory
> > > could not be "written"."
> > >
> > > Any help in resolving this is greatly appreciated.  All of our efforts
> of
> > > reinstalling PB to installing the 03 patch have failed.  You can't
even
> > > create a brand new project and then a new datawindow without it
> crashing.
> > >
> > > Thanks,
> > >
> > > Warren
> > >
> > >
> >
>
>


0
Bug
1/30/2002 8:55:32 PM
Yes, we have also tried this.  This was suggessted to us by Sybase,
unfortunately that was not the problem.  Thanks for your suggestion though.


"Bug" <fenterbug@hotmail.com> wrote in message
news:IAdo#EdqBHA.206@forums.sybase.com...
> Check for multiple copies of your PB DLL's. If you have several copies,
make
> sure they're all the same version.
>
> "Warren R" <warren_reinke@concentra.com> wrote in message
> news:KuhdxtcqBHA.204@forums.sybase.com...
> > This just started happening for all datawindows in several different
> > projects for only some PCs.  Yet opening the same exact datawindow from
my
> > PC works fine.  Weird, uh!
> >
> >
> > "Andy Neagu" <andy_neagu@hotmail.com> wrote in message
> > news:mpS8ivZqBHA.185@forums.sybase.com...
> > > Have you exported the syntax and looked at? From my experience PB
> crashes
> > in
> > > this circumstances when there are some complex fields (groups for
> > examples)
> > > and/or a "wrong" connection is active (to a different DB etc), or even
> > > worse... some field get mess inside.
> > >
> > > Andy N.
> > >
> > >
> > > "Warren R" <warren_reinke@concentra.com> ha scritto nel messaggio
> > > news:DULohJQqBHA.52@forums.sybase.com...
> > > > At work we have about 5 different developers that experienced a
> problem
> > > when
> > > > opening any datawindow from the PowerBuilder painter.  PB crashes
and
> > > halts
> > > > altogether.
> > > >
> > > > Funny thing is their PowerBuilder was working fine the day before.
My
> > > > PowerBuilder still is working fine and some other developers have
not
> > > > experienced the problem.  All of the affected PowerBuilder programs
> are
> > on
> > > > separate pc's and the developers work on different PowerBuilder
> > projects.
> > > > That makes the mystery even more confusing.
> > > >
> > > > The error is a pb70.exe - "Application Error" with the error being
> "The
> > > > instruction at "0x77fca2bf" referenced memory at "0x8328d40f".  The
> > memory
> > > > could not be "written"."
> > > >
> > > > Any help in resolving this is greatly appreciated.  All of our
efforts
> > of
> > > > reinstalling PB to installing the 03 patch have failed.  You can't
> even
> > > > create a brand new project and then a new datawindow without it
> > crashing.
> > > >
> > > > Thanks,
> > > >
> > > > Warren
> > > >
> > > >
> > >
> >
> >
>
>


0
Warren
1/31/2002 2:14:14 PM
Andy Neagu's answer is pointing you in the right direction. I spend 1/2 day 
solving this issue with one of my apps awhile back, and it turned out to be 
that there was an unresolved field in a changed datawindow. PB 7 let me 
save the window without complaint, but it corrupted the codeset so that I 
continually got crashes until I fixed it. I exported the datawindow with 
the problem, went thru the export file line by line, finally found the bad 
line, changed it, and re-imported it.

We went to PB 8 almost immediately after trying 7. PB 8 is far more stable.
0
Victoria
1/31/2002 6:29:59 PM
Victoria, was the one datawindow with an unresolved field in your project
causing all datawindows to crash upon opening them within PowerBuilder?

I just don't understand how one datawindow can cause all datawindows within
the project to crash PB upon opening any of them.  We've tried opening all
datawindows and they all crash, yet I can still open the same exact
datawindow from my machine and it works. ??? Like I said, it is a mystery
how this can be happening.

Thanks, Warren.

<Victoria> wrote in message
news:214D6B40B14CBB8A00659F3E85256B52.0073D3AC85256B50@webforums...
> Andy Neagu's answer is pointing you in the right direction. I spend 1/2
day
> solving this issue with one of my apps awhile back, and it turned out to
be
> that there was an unresolved field in a changed datawindow. PB 7 let me
> save the window without complaint, but it corrupted the codeset so that I
> continually got crashes until I fixed it. I exported the datawindow with
> the problem, went thru the export file line by line, finally found the bad
> line, changed it, and re-imported it.
>
> We went to PB 8 almost immediately after trying 7. PB 8 is far more
stable.


0
Warren
1/31/2002 6:54:05 PM
I'd double-check that you've deleted the registry key suggested earlier in
the thread.  The problem you've described *exactly* matches the ones for
which this is the solution, and I've never seen anyone posting a different
with the same symptoms.

--

Simon Caldwell
Get Real Systems Ltd
Holtby Manor, Stamford Bridge Road, York, YO19 5LL
Tel +44 (0)1904 481999 Fax +44 (0)1904 481666
Visit us at www.getrealsystems.com
Procurement Control Specialists
Controlling corporate spend and streamlining procurement processes


"Warren R" <warren_reinke@concentra.com> wrote in message
news:ApnVZloqBHA.204@forums.sybase.com...
> Victoria, was the one datawindow with an unresolved field in your project
> causing all datawindows to crash upon opening them within PowerBuilder?
>
> I just don't understand how one datawindow can cause all datawindows
within
> the project to crash PB upon opening any of them.  We've tried opening all
> datawindows and they all crash, yet I can still open the same exact
> datawindow from my machine and it works. ??? Like I said, it is a mystery
> how this can be happening.
>
> Thanks, Warren.
>
> <Victoria> wrote in message
> news:214D6B40B14CBB8A00659F3E85256B52.0073D3AC85256B50@webforums...
> > Andy Neagu's answer is pointing you in the right direction. I spend 1/2
> day
> > solving this issue with one of my apps awhile back, and it turned out to
> be
> > that there was an unresolved field in a changed datawindow. PB 7 let me
> > save the window without complaint, but it corrupted the codeset so that
I
> > continually got crashes until I fixed it. I exported the datawindow with
> > the problem, went thru the export file line by line, finally found the
bad
> > line, changed it, and re-imported it.
> >
> > We went to PB 8 almost immediately after trying 7. PB 8 is far more
> stable.
>
>


0
Simon
2/1/2002 9:57:54 AM
Well we've finally discovered our problem.  It wasn't the Registry nor a
corrupted datawindow.  It was simply a messed up printer setup on the
machine to a networked printer.  Somehow, any machine setup with that
network printer as the default would cause Powerbuilder to crash upon
opening a datawindow.  Perhaps when a datawindow is opened it reads
information from the default printer setup on the machine.

To resolve this we simply deleted all printers setup and resetup the
printers on the machine.  Everything works fine now.

Thanks for all the suggestions and I hope this never happens to another
developer out there.  It was a nightmare figuring this one out.

Warren

"Warren R" <warren_reinke@concentra.com> wrote in message
news:DULohJQqBHA.52@forums.sybase.com...
> At work we have about 5 different developers that experienced a problem
when
> opening any datawindow from the PowerBuilder painter.  PB crashes and
halts
> altogether.
>
> Funny thing is their PowerBuilder was working fine the day before.  My
> PowerBuilder still is working fine and some other developers have not
> experienced the problem.  All of the affected PowerBuilder programs are on
> separate pc's and the developers work on different PowerBuilder projects.
> That makes the mystery even more confusing.
>
> The error is a pb70.exe - "Application Error" with the error being "The
> instruction at "0x77fca2bf" referenced memory at "0x8328d40f".  The memory
> could not be "written"."
>
> Any help in resolving this is greatly appreciated.  All of our efforts of
> reinstalling PB to installing the 03 patch have failed.  You can't even
> create a brand new project and then a new datawindow without it crashing.
>
> Thanks,
>
> Warren
>
>


0
Warren
2/1/2002 8:01:56 PM
PB uses the default printer to display Datawindows.  Many Windows
applications do the same thing.  I remember Arcserve Backup crashing on me
when trying to view reports because I didn't have a default printer defined
on that server.

--
Terry Dykstra (TeamSybase)
Please state PB / OS / DB versions in your post.
MySybase http://my.sybase.com/mysybase
Search Deja: http://www.pfcguide.com/_newsgroups/search.asp

"Warren R" <warren_reinke@concentra.com> wrote in message
news:laAgAw1qBHA.204@forums.sybase.com...
> Well we've finally discovered our problem.  It wasn't the Registry nor a
> corrupted datawindow.  It was simply a messed up printer setup on the
> machine to a networked printer.  Somehow, any machine setup with that
> network printer as the default would cause Powerbuilder to crash upon
> opening a datawindow.  Perhaps when a datawindow is opened it reads
> information from the default printer setup on the machine.
>
> To resolve this we simply deleted all printers setup and resetup the
> printers on the machine.  Everything works fine now.
>
> Thanks for all the suggestions and I hope this never happens to another
> developer out there.  It was a nightmare figuring this one out.
>
> Warren
>
> "Warren R" <warren_reinke@concentra.com> wrote in message
> news:DULohJQqBHA.52@forums.sybase.com...
> > At work we have about 5 different developers that experienced a problem
> when
> > opening any datawindow from the PowerBuilder painter.  PB crashes and
> halts
> > altogether.
> >
> > Funny thing is their PowerBuilder was working fine the day before.  My
> > PowerBuilder still is working fine and some other developers have not
> > experienced the problem.  All of the affected PowerBuilder programs are
on
> > separate pc's and the developers work on different PowerBuilder
projects.
> > That makes the mystery even more confusing.
> >
> > The error is a pb70.exe - "Application Error" with the error being "The
> > instruction at "0x77fca2bf" referenced memory at "0x8328d40f".  The
memory
> > could not be "written"."
> >
> > Any help in resolving this is greatly appreciated.  All of our efforts
of
> > reinstalling PB to installing the 03 patch have failed.  You can't even
> > create a brand new project and then a new datawindow without it
crashing.
> >
> > Thanks,
> >
> > Warren
> >
> >
>
>


0
Terry
2/4/2002 4:45:56 PM
Reply:

Similar Artilces:

PowerBuilder crashes when opening datawindows
Hi, when I try edit any datawindows, PB crashes. I can open menus, windows...but not datawindows. If I right-click on the datawindow and select Edit Source, I am able to view the code but if I choose Edit it also crashes. Thanks, Joelle You need to post this in a PowerBuilder related section. This is the DataWindow.Net section. <Joelle> wrote in message news:4339b8bf.521c.1681692777@sybase.com... > Hi, > when I try edit any datawindows, PB crashes. I can open > menus, windows...but not datawindows. If I right-click on > the datawindow and select Edit Sourc...

PowerBuilder crashes when opening datawindows.
Hi, when I try edit any datawindows, PB crashes. I can open menus, windows...but not datawindows. If I right-click on the datawindow and select Edit Source, I am able to view the code but if I choose Edit it also crashes. Thanks, Joelle Remove the Layout/DataWindow key from the HKCU/Software/Sybase/PowerBuilder/<version> key in the registry. On 27 Sep 2005 14:29:30 -0700, Joelle wrote: >Hi, >when I try edit any datawindows, PB crashes. I can open >menus, windows...but not datawindows. If I right-click on >the datawindow and select Edit Source, I am able to...

Powerbuilder crashes when opening or creating datawindow
Powerbuilder crashes when I try to open or create a new datawindow in Pb9.0 I get this error AppName: pb90.exe AppVer: 9.0.0.5507 ModName: pbdev90.dll ModVer: 9.0.0.5507 Offset: 0002d23c Please help! Delete the registry key [HKEY_CURRENT_USER\Software\Sybase\PowerBuilder\9.0\Layout\Default] "Datawindow"="" PB will automatically recreate it. -- Terry Dykstra (TeamSybase) http://powerbuilder.codeXchange.sybase.com/ http://www.pb9books.com product enhancement requests: http://www.isug.com/cgi-bin/ISUG2/submit_enhancement <kith> wrote in mes...

Datawindow Open Causes Powerbuilder Crash
When trying to open an existing datawindow or create a new one, Powerbuilder crashes. I am using Powerbuilder 7.0.3. It worked fine yesterday, but this morning, no matter what datawindow I try to open, Powerbuilder crashes. I tried regenerating and rebuilding, and tried opening datawindows in several different pbls, but no luck. Any thoughts? PS I also uninstalled and re-installed 7.0.2 and the 7.0.3 upgrade. Thanks, Larry Delete the registry key [HKEY_CURRENT_USER\Software\Sybase\PowerBuilder\7.0\Layout\Default] PB will rebuild it. -- Terry Dykstra (TeamSybase) ...

Powerbuilder closing (crashing?) upon opening a datawindow
I've been trying to open/edit a particular datawindow with a single retrieval argument being passed to it, but every time I attempt to open it, Powerbuilder will prompt for the value of the argument, but regardless of entering a value and clicking ok or just cancel, Powerbuilder immediately closes. It may be a crash, but I do not receive an error message upon Powerbuilder closing and nothing is logged in event viewer. It is the only datawindow causing the problem that I've found to this point. Stranger still, the datawindow can be seen from a parent window displaying it with...

Datawindow open causes powerbuilder crash in windows 2000
When trying to open an existing datawindow or create a new one, Powerbuilder crashes. I am using Powerbuilder 7.0.2. build 8025 It worked fine yesterday, but this morning, no matter what datawindow I try to open, Powerbuilder crashes. I got this message : L'instruction � 0x77fca2bf emploie l'adresse m�moire 0xcc5d8754. La m�moire ne peut �tre "written". I tried regenerating and rebuilding, and tried opening datawindows in several different pbls, but no luck. Any thoughts? Delete the registry key [HKEY_CURRENT_USER\Software\Sybase\PowerBuilder\7.0\Layo...

PowerBuilder down on opening a datawindow.
I'm using PowerBuilder 9.0.1 on Windows XP and Oracle9i. Suddenly I cannot open any datawindow. Each time I tried to open datawindow with datawindow painter, PowerBulider gets down. Someone told me that changing default printer might help. But it didn't help. Please help me. Thanks. Several suggestions: First make a backup of the datawindow to another .pbl (you may even want to create a new .pbl just to hold the backup). 1) Try regenerating just the datawindow. 2) Try optimizing your .pbls then a full regeneration (back up all the .pbls first, again just as a ...

DataWindows crash PowerBuilder executables
I'm using PowerBuilder 7.0.3 Build 10047. Are there any .DLL's beside the PBVMxx7.dll that I need in order to use DataWindows? Whenever I try to compile and run an application that has a DataWindow the application will crash right when that DataWindow is being loaded. Any suggestions would be appreciated. Thank you PBDWE70.dll and a few others. See techdoc http://my.sybase.com/detail?id=47953 for deployment instructions. -- Terry Dykstra (TeamSybase) Please state PB / OS / DB versions in your post. MySybase http://my.sybase.com/mysybase Search Deja: http://www.pfcguid...

Powerbuilder terminate when open the library painter in PowerBuilder 9
From previous sharing, I have tried to remove the entries in registry: HKEY_CURRENT_USER\Software\Sybase\PowerBuilder\9.0\Layout\Default But it does not work for me. I have tried to re-install PowerBuilder but same result. When PB terminate, it display the following: AppName: pb90.exe App Ver: 9.0.0.5507 ModName:msvcrt.dll ModVer: 7.0.2600.2180 Offset: 000360cb Does anyone has the solution? Thanks. L K wrote: > From previous sharing, I have tried to remove the entries in > registry: > HKEY_CURRENT_USER\Software\Sybase\PowerBuilder\9.0\Layout\Default > >...

PowerBuilder Crashes on Datawindow Preview
All, We are running into a problem of PB crashing when any dw is opened due to the preview pane being available. We are running PB 10.2.1 Build 9914. The applications run fine in runtime. Only in dev preview do we see the problem. Is there a known resolution to this? Does it have to do with printer drivers? Is there a way to remove the preview pane without opening a datawindow? We've run into this problem before, about a year ago, and had to wipe the box and re-install from scratch since an uninstall and re-install did not work. Any other ideas? Many thanks. I think we&#...

Powerbuilder application "crashing" another powerbuilder application
This is a repost of the above subject since there has been some problem for messages posted on the 19th - 22nd July 2002. *************** Hi All, I have an application (App A)built using PB7.0.3 build 10077 and it seems to work fine. However, recently, another application (App B) built using PB 7.0.3 build 10047 as well was installed and it seems to trigger Dr Watson on App A. There is an embedded OCX on a "main" window on App A, which receives triggers from external applications. The OCX will then call another function sitting on another main window. That function w...

PowerBuilder crashes when trying to open a web page
Hi! I'm trying to build in PB8.02 Build 9506 and IE 5.50.4807.2300. When I go to open a page, PB crashes. I can't seem to access the pages referred to in an earlier discussion: It's a nice feature of one of the recenty security patches for IE (Q313675). See: ftp://psaftp.sybase.com/pub/private/pbpatch/pb801_weekly/8019066_fixes.html You can obtain the EBF for it at: ftp://psaftp.sybase.com/pub/private/pbpatch/pb801_weekly/8019066.zip ftp://psaftp.sybase.com/pub/private/pbpatch/pb801_weekly/web%20targets/WT801_906 6.zip Note that is an EBF, though, so y...

PowerBuilder 6.5 datawindow causes crash
I need help figuring out how to fix a datawindow that keeps crashing. This is in Power Builder version 6.5.1 retrieving data from a SQL database using a stored procedure. The datawindow has the detail hidden and several summary fields in the headers, main, group 2, and group 1. I have found that if I don't hide the detail records the datawindow doesn't cause a crash. I have applied the maintenance patch for this version. If my rusty memory serves, build 1299 of 6.5.1 was quite stable. Can you be specific about the symptoms of the crash? By "hide" do you mean se...

Why is PowerBuilder 10.5 crashing when I open a window?
This is a multi-part message in MIME format. ------=_NextPart_000_0006_01C72F19.02685BB0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I am trying to open a window that I just converted from PB 9 to PB 10.5. = Every time I do PB crashes and gives me this message: "Sybase PowerBuilder 10.5 has encountered a problem and needs to close. = We are sorry for the inconvenience." I can open the window in by Editing Source and I can regenerate it = without any errors, but as soon as I try to open it the regular way, it =...

Web resources about - Opening a datawindow crashes PowerBuilder - sybase.powerbuilder.general

PowerBuilder - Wikipedia, the free encyclopedia
PowerBuilder is an integrated development environment owned by Sybase , a division of SAP . It has been in use since 1991, peaking around 1998 ...

Sybase PowerBuilder tool readied for Microsoft's .Net
... Win32 or newer style .Net development After several years of work, Sybase is ready to deliver on the final step in its plan to move PowerBuilder ...

Jim O'Neil (@jimoneil) on Twitter
Sign in Sign up To bring you Twitter, we and our partners use cookies on our and other websites. Cookies help personalize Twitter content, tailor ...

Open Directory - Computers: Programming: Languages
about dmoz - dmoz blog - report abuse/spam - help the entire directory only in Programming/Languages Description Top : Computers : Programming ...

The HP Booth Staff (Goons) Owe Me an Apology
... when you might need to use it. For instance, when I was in the WinRunner world there were plugins for driving terminal emulators and powerbuilder ...

Contact Us - Sybase Inc
Thanks for visiting the 主页 section of Sybase.com. Here you will find information about Contact Us. For more information about Business Intelligence, ...

热门搜索 - 我的异常网
... 我的异常网 » 热门搜索 sdpnet2 移动【A111】其它用户原因鉴权失败,是什么意思啊 http:// 192.168.1.102:22578 本网站服务器位于美国,受美国法律保护 MiniUI js 破解 http://192.168.1.103:8080/ powerbuilder ...

Mobile app security: Always keep the back door locked
The best way to keep mobile apps safe is to secure the services they connect to.

10 Tech Skills That Will Instantly Net You A $100,000+ Salary
... that let's developers run Java applications. Java is highly popular language for writing web apps and custom enterprise apps. No. 8: PowerBuilder ...

Top Ranked Articles
Top Ranked Articles - Free source code and tutorials for Software developers and Architects.; Updated: 23 Feb 2013

Resources last updated: 12/7/2015 3:56:59 AM