[AccessD] Bug Report

John W. Colby jwcolby at colbyconsulting.com
Tue Aug 16 06:57:35 CDT 2005


Oh, sorry.  I was discussing my particular bug, not the "breakpoint" case.

/decompile definitely has always solved the cases I've seen of the
"breakpoint" issue.  And I see it quite often.

John W. Colby
www.ColbyConsulting.com 

Contribute your unused CPU cycles to a good cause:
http://folding.stanford.edu/

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Dettman
Sent: Tuesday, August 16, 2005 7:31 AM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] Bug Report


John,

  I thought you said the other day that this didn't work for you?

"Yea, I've seen this too.  Breaks even though the breakbpoint was removed. I
think it is the same issue, i.e. "invisible stuff" in the source code that
is not properly stripped out.

Unfortunately /decompile does not help in this case.  All that /decompile
does is throw out the pcode stream forcing a recompile of the entire source
code stream.  If the source stream is bad then the next compile will just
recreate the bad pcode."

Jim.

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of John W. Colby
Sent: Tuesday, August 16, 2005 7:17 AM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] Bug Report


A /decompile / compile / compact / repair has always fixed it for me.

John W. Colby
www.ColbyConsulting.com

Contribute your unused CPU cycles to a good cause:
http://folding.stanford.edu/

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Dettman
Sent: Tuesday, August 16, 2005 6:17 AM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] Bug Report


Rocky,

  None that I'm aware of.  I usually do a /decompile as soon as I see the
weird stuff start to happen.

  That pretty much clears it up.  If not, I go to a backup.

Jim.

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Rocky Smolin -
Beach Access Software
Sent: Monday, August 15, 2005 4:36 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Bug Report


Jim:

"code breaks on a line where a breakpoint was but is no longer"

I've had this happen as well, even more embarrassing, at the customer when
suddenly they find themselves in the code page with a yellow highlight.  Has
there been no fix for this from MS?

Rocky


--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com


-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com






More information about the AccessD mailing list