[AccessD] SPAM-LOW: Re: Access error

jwcolby jwcolby at colbyconsulting.com
Tue Jun 30 10:57:43 CDT 2009


Nowhere in my post did I EVER say that you aren't going barmy...

John W. Colby
www.ColbyConsulting.com


Max Wanadoo wrote:
> Thank you - it is nice to know that I am not going barmy....
> 
> I find it easier to cut a bunch of code into Notepad and then post it
> straight back in again rather than risk more typos though.
> 
> Max
> 
> 
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
> Sent: 30 June 2009 16:17
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Access error
> 
> You are absolutely correct Max, that is EXACTLY what is going on.
> 
> Modules contain things similar (I believe) to the old Word Perfect
> formatting stuff, where what you 
> see is definitely NOT what is in the file stream.  Sometimes things in the
> source modules gets 
> mangled, but you can't see it because it is hidden.  This is what /Decompile
> is supposed to do, 
> flush the pcode streams and recompile HOWEVER if the problem is in the
> source itself... you get back 
> the same mangled PCode stream.
> 
> By exporting to a text file, (pretty much) only what you see is what gets
> exported so the crap 
> hidden in the source file goes away.
> 
> I have spent HOURS tracking down problems like this.  My code would cause a
> page fault, Access would 
> just close without warning.  I would insert line numbers and start tracing
> through until I found the 
> offending line, then MANUALLY retype what I could visibly see, deleting the
> original and voila, no 
> more page fault.
> 
> I reiterate, what I was typing was EXACTLY what I could see on the screen
> but there was SOMETHING 
> invisible in that line of code.  As soon as I deleted the offending line,
> the problem went away. 
> Max's EatBloat would be a huge timesaver in this case.
> 
> John W. Colby
> www.ColbyConsulting.com
> 
> 
> Max Wanadoo wrote:
>> hmmm, I can't really Ken.  I just "get the feeling" that sometimes there
> may
>> be hidden control characters in modules etc, maybe caused by typing too
> fast
>> etc. You will probably have experiened the case where the code will stop
>> running on a line which appears to be a debug break point and comes up
>> hightlighted in yellow - it may have been a genuine break point at some
>> future time.  As you know, if you export code into NotePad it will strip
> any
>> control characters and leave just plain text - if you then paste it back
>> again into the module it will probably run ok the next time after a
>> compile.  Whether it is a genuine control character is impossible to say
>> because it doesn't display.
>>
>> That is all I meant by it.
>>
>> Max
>>
>>
>> On Tue, Jun 30, 2009 at 3:13 PM, Kenneth Ismert <kismert at gmail.com> wrote:
>>
>>> Max,
>>>
>>>> Not advertising here, but if you export the whole lot to text files
>>>> via EatBloat (don't know If John/Dan have re-written it yet) and
>>>> then import it into a new mdb you will drop any embedded
>>>> control characters that may be causing the problem.
>>> I've been studying this bloat/rebuild issue, and I'm unfamiliar with the
>>> 'embedded control characters' issue. Maybe I just forgot.
>>>
>>> Could you elaborate on this problem?
>>>
>>> Thanks,
>>> -Ken
>>> --
>>> 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