A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Access » General Discussion
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

COMPILER WRONG !!!



 
 
Thread Tools Display Modes
  #51  
Old October 11th, 2008, 12:52 AM posted to microsoft.public.access
David W. Fenton
external usenet poster
 
Posts: 3,373
Default COMPILER WRONG !!!

"AccessVandal via AccessMonster.com" u18947@uwe wrote in
news:8b6ef5123624a@uwe:
David W. Fenton wrote:
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.


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 http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
  #52  
Old October 11th, 2008, 07:39 AM posted to microsoft.public.access
AccessVandal via AccessMonster.com
external usenet poster
 
Posts: 461
Default COMPILER WRONG !!!

lol,

You're quick to deduced the problems that are way out.

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


Not true at all. Never had used reserved names. Period.

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


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

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.


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.

--
Please Rate the posting if helps you

Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200810/1

  #53  
Old October 11th, 2008, 09:15 PM posted to microsoft.public.access
David W. Fenton
external usenet poster
 
Posts: 3,373
Default COMPILER WRONG !!!

"AccessVandal via AccessMonster.com" u18947@uwe wrote in
news:8b7e654cfd66e@uwe:

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


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.

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.


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.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
  #54  
Old October 11th, 2008, 09:15 PM posted to microsoft.public.access
David W. Fenton
external usenet poster
 
Posts: 3,373
Default COMPILER WRONG !!!

"AccessVandal via AccessMonster.com" u18947@uwe wrote in
news:8b7e654cfd66e@uwe:

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


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.

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.


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.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
  #55  
Old October 13th, 2008, 02:10 AM posted to microsoft.public.access
AccessVandal via AccessMonster.com
external usenet poster
 
Posts: 461
Default COMPILER WRONG !!!

Unlike you, I have yet to encounter problems with class modules. Hopefully
none.lol. But I have seen functions in standard modules can cause problems to
an Access application, like changing an index of a column/field.

Good to hear that regular decompiling helps.

Well, it’s been nice talking to you. Thanks.

David W. Fenton wrote:
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.


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.


--
Please Rate the posting if helps you

Message posted via http://www.accessmonster.com

  #56  
Old November 1st, 2008, 01:35 PM posted to microsoft.public.access
PACALA_BA[_2_]
external usenet poster
 
Posts: 85
Default COMPILER WRONG !!!

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

"Douglas J. Steele" wrote:

Why bother asking us for advice if you're not going to take it?

Many different people have to you not to use the colon approach: to put no
more than one statement of code per line, and you persist in doing that.

Do you believe that making your code so difficult to read is going to make
your application smaller? You might be saving a few bytes by avoiding
carriage returns and line feeds, but it is not going to reduce your overall
size appreciably.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)


"PACALA_BA" wrote in message
...
Todays Problem




  #57  
Old November 2nd, 2008, 08:58 AM posted to microsoft.public.access
PACALA_BA[_2_]
external usenet poster
 
Posts: 85
Default COMPILER WRONG !!!

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

"PACALA_BA" wrote:

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

"Douglas J. Steele" wrote:

Why bother asking us for advice if you're not going to take it?

Many different people have to you not to use the colon approach: to put no
more than one statement of code per line, and you persist in doing that.

Do you believe that making your code so difficult to read is going to make
your application smaller? You might be saving a few bytes by avoiding
carriage returns and line feeds, but it is not going to reduce your overall
size appreciably.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)


"PACALA_BA" wrote in message
...
Todays Problem




 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 02:01 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.