COMPILER WRONG !!!

[David W. Fenton]

Hi, the same command
SetOption "Left margin", "0.1"""
while running..error, empty argument...WHY ?
in Immediate window(while code running) the same OK !!!!
and the same code-line in another databse build...OK !!!!, WHY ???

I do not have time for stupid Questions,
My MDB ( ~5MB, of text code, i wrote for 5 years, it was running
in Access 2000 wounderful, but now is there something WRONG, and
it is really ANNOYING such CRAZY errors !!!

You posted this exact response to another post. Why? Do you think
that it will get answered the second time but not the first? That it
will be clearer when we've read it twice but not when we've seen it
just once?

Sorry, but you're really behaving in a fashion that makes me want to
put you in my killfile.

 

[David W. Fenton]

Sometimes Access bombs out codes that works for years
with out problems.

This is particularly the case when you upgrade versions.

And it is often an indication that you've been following very poor
development practices in the past.

 

[David W. Fenton]

Full code of functions:

[gibberish code without line breaks deleted]

I have not time to figure out what the hell that garbage is. If you
can't format your posts in a manner that is readable, then you're
not going to get any help.

 

[David W. Fenton]

Nah..than, how do you account a simple default value on a control
refused to work on Windows Vista but works with Windows XP? Make
it into a MDE, it does not work but leave as a MDB, it works. Itƒ
Ts just a simple default value of ƒ oDate()ƒ .

Likely you've used the reserved "date" as the name of a field or
some other object. Which would be a bad development practice.

Itƒ Ts never always true about following Access developments.
Sometimes Access croaks for no reasons. Like lines of code goes
missing after compacting.

Never happens to me. But I use good development practices (COMPILE
ON DEMAND turned off, frequent DECOMPILE, compile after every major
code change).

Mind
you, it has nothing to do with poor code or programming and
nothing to do with upgrading at all.

I don't have these kinds of problems. But I use good development
practices. You may think otherwise, but that suggest that you just
don't understand what the phrase "good development practices"
actually entails.

 

[David W. Fenton]

Not true, Compile on demand is always off. Decompile, only if
there are real problem.

I decompile on a regular basis. When in heavy development mode,
about once a day, and always before distributing a new release to
the users.

No offence (not at you), there are always people make such claims.
But when problems arises, they will say, "it's not my problem".
Seen it all, even with good practices applied, problems still can
come up.

I don't encounter the kinds of problems described in this thread.
Ever.

Yes, I've had corruption in major projects (mostly with complex
interactions between standalone class modules, in fact), but it
happens very, very seldom.

Regular decompiles seem to me to be the key, as it flushes out
problems before they become difficult to resolve.

 

[PACALA_BA]

Hi, thanks for Answer
I am now removing DOUBLE-DOTS from my code (simple lines through code)
There is missing TOOL BEAUTIFY-CODE (like in FOX-PRO)
******************************************
Resume (about 70 % ready):
the Uncompiled-Database-size: ~10,5 MB (before 9MB)
The biggest MODULE: ~ 690 KB (cca. 13 000 lines of code)
In Form-events NO CRASHES ANYMORE.
****************************
But the Compiler problem is allways present...
(Difference between Code-running(Err) and
Debugger-Immediate-window (the same command-OK)

New ACCESS-11 crashes reported to Microsoft
from my WORK-PC (Not HOME-PC)...
From my site view , it seems un-believable ,
this double dots are really the MAIN-PROBLEM.
Bye

 

[PACALA_BA]

I'm sorry **COLONS** not DOUBLE-DOTS...

Hi, thanks for Answer
I am now removing DOUBLE-DOTS from my code (simple lines through code)
There is missing TOOL BEAUTIFY-CODE (like in FOX-PRO)
******************************************
Resume (about 70 % ready):
the Uncompiled-Database-size: ~10,5 MB (before 9MB)
The biggest MODULE: ~ 690 KB (cca. 13 000 lines of code)
In Form-events NO CRASHES ANYMORE.
****************************
But the Compiler problem is allways present...
(Difference between Code-running(Err) and
Debugger-Immediate-window (the same command-OK)

New ACCESS-11 crashes reported to Microsoft
from my WORK-PC (Not HOME-PC)...
From my site view , it seems un-believable ,
this double dots are really the MAIN-PROBLEM.
Bye