[AccessD] Bug Report

Charlotte Foust cfoust at infostatsystems.com
Mon Aug 15 11:03:34 CDT 2005


If you could track it down to a particular line, you're very thorough.
I couldn't get that close, and I was never sure whether the crash
happened on the call out or when the other routine accepted the call,
since the whole application evaporated and left me looking at the
Windows desktop when it happened.  In my case, the antithetical routine
wasn't necessarily being called directly, it could be several layers
down ... And I had a deadline! LOL

Charlotte Foust


-----Original Message-----
From: John W. Colby [mailto:jwcolby at colbyconsulting.com] 
Sent: Monday, August 15, 2005 8:53 AM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] Bug Report


Was it the actual line that called the other block?  This one is just
"any old line of code".  It always occurs in the OnOpen of the form,
where I am initializing classes, etc.  By setting up debug.Print
statements through the OnOpen I am able to nail down what exact line of
code it is, but it doesn't occur every time the form opens so it is a
pita to step through to actually watch the close happen.  I have caused
the close to move around however, even "pushing it out the end" of the
OnOpen back into the function that opens the form.  Truly bizarre.

I have seen this kind of stuff before however.  Back when I was working
on C2DbFrameWiz (the error handler insertion wizard) I would get
instances where the code that inserted the code into a module would just
cause a close.  It was very similar, I could "track it down" to a single
line of code.  I could go up to the previous line, type in the same code
character for character, then delete the line causing the code and the
problem would "go away" for awhile.  OTOH, If I cut the line out to the
paste buffer and pasted it back in again, I would still have the issue.


I am convinced that the source code that you see on the screen has other
things in the text stream, things that are not visible to you, the
developer.  Kind of like the old Word Perfect "show codes" where you
would cause other formatting stuff to appear.  I am convinced that the
text stream gets something embedded in it and once that something is in
the string, you are hosed.

In this case (my current application) I have gone so far as to import
the entire FE into a new blank MDB and the problem still exists.  I do
not get the "corrupted form" kind of thing that occurs with the A2K /
AXP vb dll version issue, i.e. the form module is not "corrupted" at
least not corrupted so badly that it won't export.

This is a bizarre one and very irritating to my users as you might
imagine.

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 Charlotte
Foust
Sent: Monday, August 15, 2005 11:30 AM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] Bug Report


I saw behavior like that in one of my apps once, John.  I finally
tracked it down to mixing DAO and ADO, that is, a DAO code block calling
out to an ADO block, or vice versa.  I scrubbed my code thoroughly to
prevent said circumstance and the problem went away.  One of the steps I
took was to rename my routines so that I could tell at a glance whether
they were ADO or DAO.

Charlotte Foust


-----Original Message-----
From: John W. Colby [mailto:jwcolby at colbyconsulting.com] 
Sent: Sunday, August 14, 2005 5:52 PM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] Bug Report


LOL.  There is no resolving this bug.  Access just shuts down.  Step
through the code and hit one specific line it just closes.  Not exactly
something I can fix.

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 Dan Waters
Sent: Sunday, August 14, 2005 8:44 PM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] Bug Report


Well - MS is really loosening up!  They won't charge you if it really
does turn out to be a bug.  I had to solve my bug myself for them to not
charge me!

Best of Luck!

Dan Waters

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John W. Colby
Sent: Sunday, August 14, 2005 6:41 PM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] Bug Report

The following is the response I got to my bug report:

Hello John, 
 
Thank you for contacting Microsoft Online Customer Service. 
 
I appreciate the time you have taken to provide us with the feedback. As
a Customer Service Representative, I can assist you with the support
options available with your Microsoft product. You can report bugs by
postal mail to the following address: 
 
Attn: Office Development Group
Microsoft Corporation
One Microsoft Way
Redmond, WA 98052
 
The letter should include a complete description of the bug including
the actions, software, and hardware associated with the bug and whether
or not it is consistently reproducible. 
 
You may also contact Microsoft Customer Service and speak with a support
professional about the issue and have a support case created. This
method will require you to utilize the standard options of support that
are available for your copy of Microsoft product initially. Once the
support professional is able to determine that the problem is a bug with
the software, they will not decrement the incident from warranty support
or account or issue a refund of any credit card charges if applicable. 
 
You may contact  Microsoft Developer Support Team at (800) 936-5800.
They are available 24 hours a day.  They will be able to assist you. 
 
John, I hope your issue gets resolved.
 
Thank you for using Microsoft products and services. 

Benoy
Microsoft Online Customer Service Representative

If you have any feedback about your Online Customer Service experience
please E-mail my manager Rahul Rajgopal at managers at microsoft.com
 
 

John W. Colby
www.ColbyConsulting.com 

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


-- 
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



-- 
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



-- 
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