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. |
|
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
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 |
#2
|
|||
|
|||
COMPILER WRONG !!!
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. ********************************************* |
#3
|
|||
|
|||
COMPILER WRONG !!!
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 |
#4
|
|||
|
|||
COMPILER WRONG !!!
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 |
#5
|
|||
|
|||
COMPILER WRONG !!!
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 |
#6
|
|||
|
|||
COMPILER WRONG !!!
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 |
#8
|
|||
|
|||
COMPILER WRONG !!!
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 |
#9
|
|||
|
|||
COMPILER WRONG !!!
=?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/ |
#10
|
|||
|
|||
COMPILER WRONG !!!
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... "PACALA_BA" wrote: 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 |
Thread Tools | |
Display Modes | |
|
|