COMPILER WRONG !!!

[PACALA_BA]

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/com...-9e38-51df16d4c570&dg=microsoft.public.access

 

[Allen Browne]

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

Reply to group, rather than allenbrowne at mvps dot org.

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

 

[PACALA_BA]

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

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/com...-9e38-51df16d4c570&dg=microsoft.public.access

 

[George Hepworth]

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

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

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/com...-9e38-51df16d4c570&dg=microsoft.public.access

 

[PACALA_BA]

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

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

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

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/com...-9e38-51df16d4c570&dg=microsoft.public.access

 

[George Hepworth]

Is there a question in there somewhere?

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

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

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

:

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/com...-9e38-51df16d4c570&dg=microsoft.public.access

 

[PACALA_BA]

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.

(e-mail address removed)

---------------------------------------------------------------------

Is there a question in there somewhere?

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

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







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

:

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/com...-9e38-51df16d4c570&dg=microsoft.public.access

 

[PACALA_BA]

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

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/com...-9e38-51df16d4c570&dg=microsoft.public.access

 

[David W. Fenton]

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

 

[JvC]

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/com...-9e38-51df16d4c570&dg=microsoft.public.access

 

[PACALA_BA]

Hi, Compile on Demand is OFF
i must allways Run in Debug mode
After Pseudo-Compile-Error, i Rebuild the line strSQL =...
(chr(34) Remove and Add)
Debug-menu : Compile-All,Save
and strSQL is then OK.

The most case is 1-3 Pseudo-Compile-Error
Some times it is Error free.
And than make MDE.
It Runs than dailly over Night (15 Hours)...Error Free !!!
see image -->>
http://i34.tinypic.com/71sdq8.jpg

I have NEVER seen such Errors !!!!!!
****************************
And it seems Microsoft has NO Interess about this...

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

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/com...-9e38-51df16d4c570&dg=microsoft.public.access

 

[PACALA_BA]

I have now shorten my LONG lines of code to 1/2 Length
The Maximum size = 1024 char (says Microsoft)
But It seems that the RECOMMENDED Maximum Size is NOT 1024 char

I am also MASSIVE using the double dot ':' operator
Before January 2008 , i have NONE such Problems
May be i try to recreate my code to VERY SHORT LINES.
But it is an terible thing
if (cond1 ) then x = x+ 1:y = y+1:if (cod2) then x= x-1:y = y+2:....

and i am using ONE line Select case
Select case a:case 1: x=1:case2:x=2:case else:x=10:end select

This may be an Problem (? !)

i am Allways making the same
some Little changes in MDB ~9MB
than Saveastext/Load asText, make MDE
And it works NOT 100% Error free.
the succes rate is about 30-50 %.
When i create the OK-(NONE-CRASH)MDE,
than it works WONDERFULL.....
All Access Crashes, Reported to MICROSOFT
since January 2008 about 500 CRASHES !!
*******************************
I do NOT Know the Result of this Crashes....
This MUST say MICROSOFT....
(see.....Why shoud i report to microsoft, or NOT ?)
Bye

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/com...-9e38-51df16d4c570&dg=microsoft.public.access

 

[John W. Vinson]

I have now shorten my LONG lines of code to 1/2 Length
The Maximum size = 1024 char (says Microsoft)
But It seems that the RECOMMENDED Maximum Size is NOT 1024 char

I am also MASSIVE using the double dot ':' operator
Before January 2008 , i have NONE such Problems
May be i try to recreate my code to VERY SHORT LINES.
But it is an terible thing
if (cond1 ) then x = x+ 1:y = y+1:if (cod2) then x= x-1:y = y+2:....

WHY are you trying to put all the code on one line?

It's both easier to read and easier for the compiler if you do it the normal
way:

If (cond) Then
X = X + 1
Y = Y + 1
Elseif (Cond2) Then
X = x -1
Y = Y +2
End If

and i am using ONE line Select case
Select case a:case 1: x=1:case2:x=2:case else:x=10:end select

Again:

Select Case A
Case 1
X = 1
Case 2
X = 2
Case Else
X = 10
End Select

This may be an Problem (? !)

i am Allways making the same
some Little changes in MDB ~9MB
than Saveastext/Load asText, make MDE
And it works NOT 100% Error free.
the succes rate is about 30-50 %.
When i create the OK-(NONE-CRASH)MDE,
than it works WONDERFULL.....
All Access Crashes, Reported to MICROSOFT
since January 2008 about 500 CRASHES !!
*******************************
I do NOT Know the Result of this Crashes....
This MUST say MICROSOFT....
(see.....Why shoud i report to microsoft, or NOT ?)

If you're assuming that posting in this newsgroup is "reporting to Microsoft"
you should be aware that it is NOT. These newsgroups are peer support groups;
everyone who answers questions here is an unpaid volunteer. Even the
occasional posts from Microsoft employees are (as far as I know) on their own
time.

I do *not* think you have a bug.

I think you have a very individual and probably flawed programming style, for
reasons which I do not understand.

Try writing your code without multiple lines per line, and without hugely long
single lines. I honestly believe it will work better.

 

[PACALA_BA]

Hi, thanks for the Answer
1.
I HAVE reported 'Access-Crashes' to Microsoft
( we are sorry for the inconvinience..., why shoud i report to microsoft)

2. why long lines ?
I have LARGE-NON-TABLES/PROGRAM DATABASE (MODULES ~5.5MB)
The code is more readable, but from 'Overview-Sight' (My opinion),
When you are interesting in Detail of Code it is Opaque/Not very good
readable.
When i am writing code,
allways it is SHORT, after DEBUG-OK, i have change it to LONG-LINE.
Ok, i can change it BACK.
I have shorten NOW my VERY-LONG-LINES, 'First' Result is , it seems more
stabil...

3.but BIG-PROBLEM is this wrong-compiler-example
http://i34.tinypic.com/71sdq8.jpg ;
that probably makes this ~300 ACCESS-CRASHES , that i HAVE REPORTED to
Microsoft.

Bye

 

[John W. Vinson]

Hi, thanks for the Answer
1.
I HAVE reported 'Access-Crashes' to Microsoft
( we are sorry for the inconvinience..., why shoud i report to microsoft)

2. why long lines ?
I have LARGE-NON-TABLES/PROGRAM DATABASE (MODULES ~5.5MB)

No. You have a *TINY* database. 50MByte is getting a bit large; 1000MByte is
getting too big. 5.5MByte is a *very small database*.

The code is more readable, but from 'Overview-Sight' (My opinion),
When you are interesting in Detail of Code it is Opaque/Not very good
readable.

So scrolling horizontally across three or four screens is somehow *more*
readable?

When i am writing code,
allways it is SHORT, after DEBUG-OK, i have change it to LONG-LINE.
WHY!!!!???

Ok, i can change it BACK.
I have shorten NOW my VERY-LONG-LINES, 'First' Result is , it seems more
stabil...

Well... ok. So you've found at least one source of the problem.

3.but BIG-PROBLEM is this wrong-compiler-example
http://i34.tinypic.com/71sdq8.jpg ;

I have NO idea what that screen means.

that probably makes this ~300 ACCESS-CRASHES , that i HAVE REPORTED to
Microsoft.

What would you like me - an unpaid volunteer donating my time on this
newsgroup - to do? What result do you hope to get from posting to this
newsgroup?

 

[PACALA_BA]

BIG-PROBLEM is this wrong-compiler-example
http://i34.tinypic.com/71sdq8.jpg ;

Here is the String cSQL not correctly created !!!!
The Compiler DO NOT SEE the value of gkII_cKRA_SKR !!!!!!!!!

public const gkII_cKRA_SKR = "LAB"
' cSQL = "SOME-STRING" ....the actual vlue
If (LN_FLD_SEL_CNT < 255) Then
cSQL = cSQL & ",I0." & gkII_cKRA_SKR ' <--- SEE NOTICE DOWN
LN_FLD_SEL_CNT = LN_FLD_SEL_CNT + 1
endif
NOTICE:
In the watches window, the line with RED arrows
cSQL = "SOME-STRING,I0." ..the WRONG-current value of cSQL
->> WITHOUT public const gkII_cKRA_SKR ("LAB") ,WHY ?????
Question:
In the watches window, the line with GREEN arrows
cSQL = cSQL & ",I0." & gkII_cKRA_SKR ..the current value of CODE-LINE is
"SOME-STRING,I0.,I0.LAB"...
Here is added "LAB", that is OK...!!!!!!!!!!, but only in WATCH-WINDOW

Resume:
Why is there DIFFERENCE between Compiler and DEBUG ???
*******************************************
than the string is used for an connection
Connection.Execute cSQL
and because the string cSQL is Wrong , execution failes.....

 

[David W. Fenton]

BIG-PROBLEM is this wrong-compiler-example
http://i34.tinypic.com/71sdq8.jpg ;

We have not idea what that screenshot means. If you want help,
you're going to have to explain it.

 

[John W. Vinson]

Hi, Compile on Demand is OFF
i must allways Run in Debug mode
After Pseudo-Compile-Error, i Rebuild the line strSQL =...
(chr(34) Remove and Add)
Debug-menu : Compile-All,Save
and strSQL is then OK.

The most case is 1-3 Pseudo-Compile-Error
Some times it is Error free.
And than make MDE.
It Runs than dailly over Night (15 Hours)...Error Free !!!
see image -->>
http://i34.tinypic.com/71sdq8.jpg

OK... so when you export your VBA code to a text file, that text file exeeds
5MByte? Yes, that is awfully big.

It LOOKS like you are either somehow trying to construct VBA labels from
variables - which I would not have thought possible - or you're treating the :
character as a statement delimiter. It isn't; the statement delimiter is a
semicolon ;. The colon (double dot) operator : delimits a statement label from
the statement. This is perhaps why you're getting the undefined label error.

Could you describe briefly what real-life problem this database is intended to
solve, and what role your awfully big VBA routine plays in this purpose?

 

[Clif McIrvin]

On Thu, 2 Oct 2008 08:22:14 -0700, PACALA_BA

It LOOKS like you are either somehow trying to construct VBA labels
from
variables - which I would not have thought possible - or you're
treating the :
character as a statement delimiter. It isn't; the statement delimiter
is a
semicolon ;. The colon (double dot) operator : delimits a statement
label from
the statement. This is perhaps why you're getting the undefined label
error.

Whoa, John, you lost me there! the full colon has always been a line
continuation character in MS Basic from the very early days, hasn't it?

Quoting from the installed VBA help file on the If ... Then ... Else
statement:
Note With the single-line form, it is possible to have multiple
statements executed as the result of an If...Then decision. All
statements must be on the same line and separated by colons, as in the
following statement:

If A > 10 Then A = A + 1 : B = B + A : C = C + B

--end quote--

I didn't attempt to study Pacala's code; if he has a line with a
non-blank in column 1 and no spaces before the full colon, yes, the
compiler would attempt to make that token into a label.

 

[John W. Vinson]

Whoa, John, you lost me there! the full colon has always been a line
continuation character in MS Basic from the very early days, hasn't it?

My apologies to you and to PACALA_BA. You're quite right of course.