COMPILER WRONG !!!

Some times happens this:
It is MS ACCESS 2003, VERY LARGE PROGRAM-DB (MDE=9MB,MDB=15MB)
There are NO BASIC ERRORS
There are COMPILE ERRORS !!!!!!!!!!!!!!!
strSQL = "select * from [" & lcTAbleNAme & "] where ...." & lcWhere & "...."
After compile, the string is SHORTEN
CNN.Execute strSQL
Debug.print =
strSQL = "select * from ["
I must Compile not ONE-times, but 2-3 Times, and then is OK.
*********************************************


----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/comm....public.access

Hopefully some of these suggestions will help:

1. Make sure Name AutoCorrect is off

2. Decompile.

3. Remove any library references you don't really have to have.

4. Make sure Compile On Demand is turned off, and break set to 'Unhandled
errors' (Tools | Options, in the code window.)

5. Make sure *all* modules use Option Explicit.

6. Solve all the compile errors before you run the code.

7. Do not edit the VBA code in break mode (i.e. always switch a form to
design view before you modify the code in its module.

8. Avoid using the AccessField type, i.e. place a control on the form and
refer to do the control; do not refer directly to a field in the form's
RecordSource.

9. Ensure nothing is causing a write to be interrupted.

More info about the first 4:
http://allenbrowne.com/recover.html
and the later ones:
http://allenbrowne.com/ser-25.html

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"PACALA_BA" wrote in message
...
Some times happens this:
It is MS ACCESS 2003, VERY LARGE PROGRAM-DB (MDE=9MB,MDB=15MB)
There are NO BASIC ERRORS
There are COMPILE ERRORS !!!!!!!!!!!!!!!
strSQL = "select * from [" & lcTAbleNAme & "] where ...." & lcWhere &
"...."
After compile, the string is SHORTEN
CNN.Execute strSQL
Debug.print =
strSQL = "select * from ["
I must Compile not ONE-times, but 2-3 Times, and then is OK.
*********************************************

Hi Allen Browne
Ok, thank you.
But WHAT SAYS MICROSOFT...?
****************************
All your suggestion are True in My MDB.
This happens Permanently...!!!!
Solution:
1.All Modules Reload [Export & Import]
2.Debugger: Run, When Error occurs( I must pseudo-edit this line), than
Compile
and Continue....

"PACALA_BA" wrote:

Some times happens this:
It is MS ACCESS 2003, VERY LARGE PROGRAM-DB (MDE=9MB,MDB=15MB)
There are NO BASIC ERRORS
There are COMPILE ERRORS !!!!!!!!!!!!!!!
strSQL = "select * from [" & lcTAbleNAme & "] where ...." & lcWhere & "...."
After compile, the string is SHORTEN
CNN.Execute strSQL
Debug.print =
strSQL = "select * from ["
I must Compile not ONE-times, but 2-3 Times, and then is OK.
*********************************************


----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/comm....public.access

I suspect that at least part of the problem here is language related and
that your use of the term "permanently" might be something slightly
different from what you intend it to mean. "Permanently" means a condition
does not change, as in "the moon is in a permanent orbit around the earth".

I believe that the term you would want to use to describe your problem is
"repeatedly"or "consistently" or even "predictably". However, "permanently"
would mean that once it crashes, it can't ever be restored, which is clearly
not your case. It happens over and over, but you can recover from it. That's
NOT a permanent crash.

The second thing is that could be language related is your question: "But
WHAT SAYS MICROSOFT...?" That can be interpreted in two different ways as
well. It's not clear meaning which you intend.

However, if you are asking for a response from Microsoft in this forum, you
will not get one. You've already been told two or three times that Microsoft
employees do not respond in this forum. They don't.

IF YOU WANT HELP DIRECTLY FROM MICROSOFT YOU WILL NEED TO FOLLOW LARRY'S
SUGGESTION PREVIOUSLY OFFERED ON OBTAINING PAID HELP FROM THEIR SUPPORT
SITE.

Here you will get suggestions from volunteers who can only offer suggestions
if they get enough information from you to do so. Several people have
offered their suggestions. At this point, you can either follow their
suggestions, or you can continue to complain. If you've tried the
suggestions offered by Larry and David, and still have no resolution, then
post back with the SPECIFIC section of code that fails to compile, not just
a snippet from one line.

Finally, 15MB is NOT a large Access database. 150MB is a fairly good sized
Access database. 500MB is a big Access database. However, in theory Access
databases can be as large as 2,000MB (that's 2 GB). You have a long way to
go before size should be an issue in any way.

I believe both Larry and David suggested you may have issues with the number
of internal objects in your database, but that is based on educated guesses
about the kinds of common problems we see as VOLUNTEERS on this forum.

Focus on the compile errors. Post here the VBA that fails to complie. The
entire VBA, not a snippet.
From there you might begin to get useful suggestions.

George







"PACALA_BA" wrote in message
...
Hi Allen Browne
Ok, thank you.
But WHAT SAYS MICROSOFT...?
****************************
All your suggestion are True in My MDB.
This happens Permanently...!!!!
Solution:
1.All Modules Reload [Export & Import]
2.Debugger: Run, When Error occurs( I must pseudo-edit this line), than
Compile
and Continue....

"PACALA_BA" wrote:

Some times happens this:
It is MS ACCESS 2003, VERY LARGE PROGRAM-DB (MDE=9MB,MDB=15MB)
There are NO BASIC ERRORS
There are COMPILE ERRORS !!!!!!!!!!!!!!!
strSQL = "select * from [" & lcTAbleNAme & "] where ...." & lcWhere
& "...."
After compile, the string is SHORTEN
CNN.Execute strSQL
Debug.print =
strSQL = "select * from ["
I must Compile not ONE-times, but 2-3 Times, and then is OK.
*********************************************


----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the
"I
Agree" button in the message pane. If you do not see the button, follow
this
link to open the suggestion in the Microsoft Web-based Newsreader and
then
click "I Agree" in the message pane.

http://www.microsoft.com/office/comm....public.access

Hi
it is an LARGE-PROGRAM (NOT-DATA) database 15 MB/MDB 9MB/MDE
PAID HELP....ok, last possibility.
I am old FOX-PRO user (since 1998) ,
i had moved all my code to Access-2003 (since 2004).
But i had never seen such errors...

My MEMORY testing , today is O.K.
**************************
I try to create an admin/public-version with this error....

"George Hepworth" wrote:

I suspect that at least part of the problem here is language related and
that your use of the term "permanently" might be something slightly
different from what you intend it to mean. "Permanently" means a condition
does not change, as in "the moon is in a permanent orbit around the earth".

I believe that the term you would want to use to describe your problem is
"repeatedly"or "consistently" or even "predictably". However, "permanently"
would mean that once it crashes, it can't ever be restored, which is clearly
not your case. It happens over and over, but you can recover from it. That's
NOT a permanent crash.

The second thing is that could be language related is your question: "But
WHAT SAYS MICROSOFT...?" That can be interpreted in two different ways as
well. It's not clear meaning which you intend.

However, if you are asking for a response from Microsoft in this forum, you
will not get one. You've already been told two or three times that Microsoft
employees do not respond in this forum. They don't.

IF YOU WANT HELP DIRECTLY FROM MICROSOFT YOU WILL NEED TO FOLLOW LARRY'S
SUGGESTION PREVIOUSLY OFFERED ON OBTAINING PAID HELP FROM THEIR SUPPORT
SITE.

Here you will get suggestions from volunteers who can only offer suggestions
if they get enough information from you to do so. Several people have
offered their suggestions. At this point, you can either follow their
suggestions, or you can continue to complain. If you've tried the
suggestions offered by Larry and David, and still have no resolution, then
post back with the SPECIFIC section of code that fails to compile, not just
a snippet from one line.

Finally, 15MB is NOT a large Access database. 150MB is a fairly good sized
Access database. 500MB is a big Access database. However, in theory Access
databases can be as large as 2,000MB (that's 2 GB). You have a long way to
go before size should be an issue in any way.

I believe both Larry and David suggested you may have issues with the number
of internal objects in your database, but that is based on educated guesses
about the kinds of common problems we see as VOLUNTEERS on this forum.

Focus on the compile errors. Post here the VBA that fails to complie. The
entire VBA, not a snippet.
From there you might begin to get useful suggestions.

George







"PACALA_BA" wrote in message
...
Hi Allen Browne
Ok, thank you.
But WHAT SAYS MICROSOFT...?
****************************
All your suggestion are True in My MDB.
This happens Permanently...!!!!
Solution:
1.All Modules Reload [Export & Import]
2.Debugger: Run, When Error occurs( I must pseudo-edit this line), than
Compile
and Continue....

"PACALA_BA" wrote:

Some times happens this:
It is MS ACCESS 2003, VERY LARGE PROGRAM-DB (MDE=9MB,MDB=15MB)
There are NO BASIC ERRORS
There are COMPILE ERRORS !!!!!!!!!!!!!!!
strSQL = "select * from [" & lcTAbleNAme & "] where ...." & lcWhere
& "...."
After compile, the string is SHORTEN
CNN.Execute strSQL
Debug.print =
strSQL = "select * from ["
I must Compile not ONE-times, but 2-3 Times, and then is OK.
*********************************************


----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the
"I
Agree" button in the message pane. If you do not see the button, follow
this
link to open the suggestion in the Microsoft Web-based Newsreader and
then
click "I Agree" in the message pane.

http://www.microsoft.com/office/comm....public.access

Is there a question in there somewhere?



"PACALA_BA" wrote in message
...
Hi
it is an LARGE-PROGRAM (NOT-DATA) database 15 MB/MDB 9MB/MDE
PAID HELP....ok, last possibility.
I am old FOX-PRO user (since 1998) ,
i had moved all my code to Access-2003 (since 2004).
But i had never seen such errors...

My MEMORY testing , today is O.K.
**************************
I try to create an admin/public-version with this error....

"George Hepworth" wrote:

I suspect that at least part of the problem here is language related and
that your use of the term "permanently" might be something slightly
different from what you intend it to mean. "Permanently" means a
condition
does not change, as in "the moon is in a permanent orbit around the
earth".

I believe that the term you would want to use to describe your problem is
"repeatedly"or "consistently" or even "predictably". However,
"permanently"
would mean that once it crashes, it can't ever be restored, which is
clearly
not your case. It happens over and over, but you can recover from it.
That's
NOT a permanent crash.

The second thing is that could be language related is your question: "But
WHAT SAYS MICROSOFT...?" That can be interpreted in two different ways as
well. It's not clear meaning which you intend.

However, if you are asking for a response from Microsoft in this forum,
you
will not get one. You've already been told two or three times that
Microsoft
employees do not respond in this forum. They don't.

IF YOU WANT HELP DIRECTLY FROM MICROSOFT YOU WILL NEED TO FOLLOW LARRY'S
SUGGESTION PREVIOUSLY OFFERED ON OBTAINING PAID HELP FROM THEIR SUPPORT
SITE.

Here you will get suggestions from volunteers who can only offer
suggestions
if they get enough information from you to do so. Several people have
offered their suggestions. At this point, you can either follow their
suggestions, or you can continue to complain. If you've tried the
suggestions offered by Larry and David, and still have no resolution,
then
post back with the SPECIFIC section of code that fails to compile, not
just
a snippet from one line.

Finally, 15MB is NOT a large Access database. 150MB is a fairly good
sized
Access database. 500MB is a big Access database. However, in theory
Access
databases can be as large as 2,000MB (that's 2 GB). You have a long way
to
go before size should be an issue in any way.

I believe both Larry and David suggested you may have issues with the
number
of internal objects in your database, but that is based on educated
guesses
about the kinds of common problems we see as VOLUNTEERS on this forum.

Focus on the compile errors. Post here the VBA that fails to complie. The
entire VBA, not a snippet.
From there you might begin to get useful suggestions.

George







"PACALA_BA" wrote in message
...
Hi Allen Browne
Ok, thank you.
But WHAT SAYS MICROSOFT...?
****************************
All your suggestion are True in My MDB.
This happens Permanently...!!!!
Solution:
1.All Modules Reload [Export & Import]
2.Debugger: Run, When Error occurs( I must pseudo-edit this line), than
Compile
and Continue....

"PACALA_BA" wrote:

Some times happens this:
It is MS ACCESS 2003, VERY LARGE PROGRAM-DB (MDE=9MB,MDB=15MB)
There are NO BASIC ERRORS
There are COMPILE ERRORS !!!!!!!!!!!!!!!
strSQL = "select * from [" & lcTAbleNAme & "] where ...." &
lcWhere
& "...."
After compile, the string is SHORTEN
CNN.Execute strSQL
Debug.print =
strSQL = "select * from ["
I must Compile not ONE-times, but 2-3 Times, and then is OK.
*********************************************


----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click
the
"I
Agree" button in the message pane. If you do not see the button,
follow
this
link to open the suggestion in the Microsoft Web-based Newsreader and
then
click "I Agree" in the message pane.

http://www.microsoft.com/office/comm....public.access

I have an Powerpoint file ACC_COMPILER_ERR_01.ppt
strOut = str1 & str2..in program lines
strOut = str1 ....if running (WITHOUT str2 !!!)
How can i send it to YOU ?
I have large-Program-Database , size=15MB (NOT-DATA-Tables)
I make links to large Data-tables-Database size=2GB
---------------------------------
Thank
-----------------------------------------------------------
see....
Microsoft BUG in app.LoadFromText acModule,...
************************************
Hi, This is an FULL-ACCESS-2003-line:
Dim lc_KNR_TAB_FA$, LN_BBA_SER&, ll_POC_MAN_DTM As Boolean, ln_FLT_IMX As
eIII_IMX_GRP_Enum, lc_cur_TR$, lcSftRJ$, lc_FLD_CDF$, lc_FLD_FRB$,
lc_FLD_MR$, lc_FLD_ZTP$, lc_FLD_W_NAS_S$, lc_FLD_W_VYP_S$, strFROM_EXE$,
strWHERE_EXE$, lc_VERS$, strSUBQRY_EXE$, lc_KNR_TAB_BWM$, lc_KNR_TAB_AP$,
lc_KNR_TAB_SJ$, lc_cur_SJ$, strWHERE_B$, strWHERE_DTM_1$, strWHERE_DTM_2$,
strWHERE_FFFK$, ll_Analyze As Boolean, ll_TRM_SER_ALL As Boolean,
ll_Analyze_CUR As Boolean, strWHERE_MR$, strWHERE_FRB$, strWHERE_OLD$,
strWHERE_NEW$, strWHERE_BRW_FLT$, ll_make_color_MR_INI As Boolean,
ll_make_color_FRBVYB_INI As Boolean, lc_TMP_FLT$, I_MAX_ATR_INI&,
i_Rows_TAB_CUR&, ll_BrowseTable As Boolean, ll_DEL_TAB_OUT As Boolean,
lc_MATCH_NO$, ll_MATCH As Boolean, ll_DISK_FULL As Boolean, ln_free_DBC As
eDBCounterEnum, ln_TT_TYPE As eTTTW_KUS_Enum, ll_TR_ZTP_MAX As Boolean,
ll_KUS_KBX As Boolean, ll_KUS_KTX As Boolean, lc_CUR_SER$, ll_TGNCurSer As
Boolean, la_KnrFldZTP As Variant, lc_BrwFlt_INI$, ll_BrwFlt_SET As Boolean,
ll_SHW_OUT As Boolean
app.LoadFromText acModule, Name, FileName
Two times TRY, two times the same Error.....
The last 'n' is cut and paste to the new line !!!
************************************
I had Reloaded my Large-program-database to TXT, and than back.
I works MORE-better, but there are ALLWAS CRASHES !!!
There must be something WRONG else.



---------------------------------------------------------------------
"George Hepworth" wrote:

Is there a question in there somewhere?



"PACALA_BA" wrote in message
...
Hi
it is an LARGE-PROGRAM (NOT-DATA) database 15 MB/MDB 9MB/MDE
PAID HELP....ok, last possibility.
I am old FOX-PRO user (since 1998) ,
i had moved all my code to Access-2003 (since 2004).
But i had never seen such errors...

My MEMORY testing , today is O.K.
**************************
I try to create an admin/public-version with this error....

"George Hepworth" wrote:

I suspect that at least part of the problem here is language related and
that your use of the term "permanently" might be something slightly
different from what you intend it to mean. "Permanently" means a
condition
does not change, as in "the moon is in a permanent orbit around the
earth".

I believe that the term you would want to use to describe your problem is
"repeatedly"or "consistently" or even "predictably". However,
"permanently"
would mean that once it crashes, it can't ever be restored, which is
clearly
not your case. It happens over and over, but you can recover from it.
That's
NOT a permanent crash.

The second thing is that could be language related is your question: "But
WHAT SAYS MICROSOFT...?" That can be interpreted in two different ways as
well. It's not clear meaning which you intend.

However, if you are asking for a response from Microsoft in this forum,
you
will not get one. You've already been told two or three times that
Microsoft
employees do not respond in this forum. They don't.

IF YOU WANT HELP DIRECTLY FROM MICROSOFT YOU WILL NEED TO FOLLOW LARRY'S
SUGGESTION PREVIOUSLY OFFERED ON OBTAINING PAID HELP FROM THEIR SUPPORT
SITE.

Here you will get suggestions from volunteers who can only offer
suggestions
if they get enough information from you to do so. Several people have
offered their suggestions. At this point, you can either follow their
suggestions, or you can continue to complain. If you've tried the
suggestions offered by Larry and David, and still have no resolution,
then
post back with the SPECIFIC section of code that fails to compile, not
just
a snippet from one line.

Finally, 15MB is NOT a large Access database. 150MB is a fairly good
sized
Access database. 500MB is a big Access database. However, in theory
Access
databases can be as large as 2,000MB (that's 2 GB). You have a long way
to
go before size should be an issue in any way.

I believe both Larry and David suggested you may have issues with the
number
of internal objects in your database, but that is based on educated
guesses
about the kinds of common problems we see as VOLUNTEERS on this forum.

Focus on the compile errors. Post here the VBA that fails to complie. The
entire VBA, not a snippet.
From there you might begin to get useful suggestions.

George







"PACALA_BA" wrote in message
...
Hi Allen Browne
Ok, thank you.
But WHAT SAYS MICROSOFT...?
****************************
All your suggestion are True in My MDB.
This happens Permanently...!!!!
Solution:
1.All Modules Reload [Export & Import]
2.Debugger: Run, When Error occurs( I must pseudo-edit this line), than
Compile
and Continue....

"PACALA_BA" wrote:

Some times happens this:
It is MS ACCESS 2003, VERY LARGE PROGRAM-DB (MDE=9MB,MDB=15MB)
There are NO BASIC ERRORS
There are COMPILE ERRORS !!!!!!!!!!!!!!!
strSQL = "select * from [" & lcTAbleNAme & "] where ...." &
lcWhere
& "...."
After compile, the string is SHORTEN
CNN.Execute strSQL
Debug.print =
strSQL = "select * from ["
I must Compile not ONE-times, but 2-3 Times, and then is OK.
*********************************************


----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click
the
"I
Agree" button in the message pane. If you do not see the button,
follow
this
link to open the suggestion in the Microsoft Web-based Newsreader and
then
click "I Agree" in the message pane.

http://www.microsoft.com/office/comm....public.access

hi, an typical unbelievable COMPILER ERROR !!!!
***********************************
Singel User/ Secure ACCES-2003 Database (MDE+MDW)
( it happens also after SaveAsText/loadAsText)
http://i34.tinypic.com/71sdq8.jpg
**************************
the conpiler DO NOT SEE some part of the line
(an public constant)
ther is an difference between WATCH and Run Variable !!!!


"PACALA_BA" wrote:

Some times happens this:
It is MS ACCESS 2003, VERY LARGE PROGRAM-DB (MDE=9MB,MDB=15MB)
There are NO BASIC ERRORS
There are COMPILE ERRORS !!!!!!!!!!!!!!!
strSQL = "select * from [" & lcTAbleNAme & "] where ...." & lcWhere & "...."
After compile, the string is SHORTEN
CNN.Execute strSQL
Debug.print =
strSQL = "select * from ["
I must Compile not ONE-times, but 2-3 Times, and then is OK.
*********************************************


----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/comm....public.access

=?Utf-8?B?UEFDQUxBX0JB?= wrote
in :

***********************************
Singel User/ Secure ACCES-2003 Database (MDE+MDW)
( it happens also after SaveAsText/loadAsText)
http://i34.tinypic.com/71sdq8.jpg
**************************
the conpiler DO NOT SEE some part of the line
(an public constant)
ther is an difference between WATCH and Run Variable !!!!

Are you developing with COMPILE ON DEMAND turned OFF? If not, turn
it off.

Have you decompiled your app and recompiled it?

The compiler may be compiling something other than what you think
it's compiling (i.e., not the canonical code that you typed, but
some of the saved p-code from previous compilation operations). See
this article for an explanation:

http://trigeminal.com/usenet/usenet004.asp?1033

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

Pacala_BA,

Could you please do a

debug.print strSQL, lcTableName, lcWhere

before the CNN.Execute, and post the results? Please print the entire
string for the concantenation, too. It might help!

John

PACALA_BA formulated the question :
Some times happens this:
It is MS ACCESS 2003, VERY LARGE PROGRAM-DB (MDE=9MB,MDB=15MB)
There are NO BASIC ERRORS
There are COMPILE ERRORS !!!!!!!!!!!!!!!
strSQL = "select * from [" & lcTAbleNAme & "] where ...." & lcWhere &
"...." After compile, the string is SHORTEN
CNN.Execute strSQL
Debug.print =
strSQL = "select * from ["
I must Compile not ONE-times, but 2-3 Times, and then is OK.
*********************************************


----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/comm....public.access