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 |
#21
|
|||
|
|||
COMPILER WRONG !!!
Hi, WHAT is not clear, i am ready to EXPLAIN it.....
-------- cSQL = cSQL & ",I0." & gkII_cKRA_SKR..this CODE-LINE is in MODULE -------- cSQL = cSQL & ",I0.".....when running CODE, the compiler DO-NOT see the value of public constant gkII_cKRA_SKR = "LAB"...!!!!! WHY ???? ------------------------------------------------------------------------------- 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" wrote: =?Utf-8?B?UEFDQUxBX0JB?= wrote in : 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. -- David W. Fenton http://www.dfenton.com/ usenet at dfenton dot com http://www.dfenton.com/DFA/ |
#22
|
|||
|
|||
COMPILER WRONG !!!
=?Utf-8?B?UEFDQUxBX0JB?= wrote
in : WHAT is not clear, i am ready to EXPLAIN it..... You're using a piece of software to monitor what's going on and it's not Access. This information is useless to us, and I'm not interested in figuring out what it all means, nor in reading your explanation of what it means. You haven't shown anything at all as a compiler error, and we've not seen the code that you say is compiling wrong, so are as I recall. I don't have much interest in trying to wade through spaghetti posts in order find out WTF you're trying to say. If you can't lay it out clearly, then you're not going to get an answer. -- David W. Fenton http://www.dfenton.com/ usenet at dfenton dot com http://www.dfenton.com/DFA/ |
#24
|
|||
|
|||
COMPILER WRONG !!!
=?Utf-8?B?UEFDQUxBX0JB?= wrote
in : After Compile is all OK, NO-Errors (But it is NOT REALLY TRUE !!), when executing SQL-string , comes an Error: ***Invalid syntax of SQL-String***, because the Acces-System/Compiler DO-NOT see the value of one public constant (=NullSting) !!!!, Why not use the built-in Access constant, vbNullString, instead? Then you don't have to worry about defining your own constants. but in Debugger/Watch IS the value of public constant ANOTHER (="LAB") After 'PSEUDO-LINE-EDIT' (Value before and after the same) it is OK, and runs Error-free over night (15 Hours). I have NEVER seen such error !!! I have no idea what the hell you are talking about here. And you didn't post the code that you say is compiling wrong, so I really can't suggest anything at all. It looks to me as though you don't actually want any assistance as you're making it as hard as possible for anyone to even comprehend your supposed problem, let alone offer a suggested solution. -- David W. Fenton http://www.dfenton.com/ usenet at dfenton dot com http://www.dfenton.com/DFA/ |
#25
|
|||
|
|||
COMPILER WRONG !!!
PACALA_BA wrote:
After Compile is all OK, NO-Errors (But it is NOT REALLY TRUE !!), The compile did compile successfully. But you will still get runtime errors which is what you have. when executing SQL-string , comes an Error: ***Invalid syntax of SQL-String***, because the Acces-System/Compiler DO-NOT see the value of one public constant (=NullSting) !!!!, but in Debugger/Watch IS the value of public constant ANOTHER (="LAB") After 'PSEUDO-LINE-EDIT' (Value before and after the same) it is OK, and runs Error-free over night (15 Hours). Like David said. Post your code. Then we can tell you what the problem is. Tony -- Tony Toews, Microsoft Access MVP Please respond only in the newsgroups so that others can read the entire thread of messages. Microsoft Access Links, Hints, Tips & Accounting Systems at http://www.granite.ab.ca/accsmstr.htm Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/ |
#26
|
|||
|
|||
COMPILER WRONG !!!
Hi, the CODE is SIMPLE
My_public_const = "ABC" strSQL = "SOME-STRING" & My_public_const when running.... strSQL = "SOME-STRING" ...**MISSING** My_public_const, WHY ?? Debugger-Watch window.... strSQL = "SOME-STRING" & My_public_const...O.K. -------------- I am building allways the same MDE, with little changes This is allways problem, but allways ANOTHER-CODE-PLACE...!!!??? I have implemented an TEST-RUN, because of this Annoying errors.... "David W. Fenton" wrote: =?Utf-8?B?UEFDQUxBX0JB?= wrote in : After Compile is all OK, NO-Errors (But it is NOT REALLY TRUE !!), when executing SQL-string , comes an Error: ***Invalid syntax of SQL-String***, because the Acces-System/Compiler DO-NOT see the value of one public constant (=NullSting) !!!!, Why not use the built-in Access constant, vbNullString, instead? Then you don't have to worry about defining your own constants. but in Debugger/Watch IS the value of public constant ANOTHER (="LAB") After 'PSEUDO-LINE-EDIT' (Value before and after the same) it is OK, and runs Error-free over night (15 Hours). I have NEVER seen such error !!! I have no idea what the hell you are talking about here. And you didn't post the code that you say is compiling wrong, so I really can't suggest anything at all. It looks to me as though you don't actually want any assistance as you're making it as hard as possible for anyone to even comprehend your supposed problem, let alone offer a suggested solution. -- David W. Fenton http://www.dfenton.com/ usenet at dfenton dot com http://www.dfenton.com/DFA/ |
#27
|
|||
|
|||
COMPILER WRONG !!!
Hi, In the CODE are NO-PROGRAMMERS-ERRORS (my Opinion)
This happens Allways, in 1-2 code-places (most case), sometimes over 10. After Pseudo-line-edit (Before/After the same) ....it is ALL-OK And Problem CODE is allways in ANOTHER-Code-Place BIG-PROBLEM is this wrong-compiler-example Here is the CORE of CODE....or something else missing ? ***************************************** http://i34.tinypic.com/71sdq8.jpg ; I can place the whole code here , but you will see Nothing ....(my Opinion) There must be Something else WRONG... "Tony Toews [MVP]" wrote: PACALA_BA wrote: After Compile is all OK, NO-Errors (But it is NOT REALLY TRUE !!), The compile did compile successfully. But you will still get runtime errors which is what you have. when executing SQL-string , comes an Error: ***Invalid syntax of SQL-String***, because the Acces-System/Compiler DO-NOT see the value of one public constant (=NullSting) !!!!, but in Debugger/Watch IS the value of public constant ANOTHER (="LAB") After 'PSEUDO-LINE-EDIT' (Value before and after the same) it is OK, and runs Error-free over night (15 Hours). Like David said. Post your code. Then we can tell you what the problem is. Tony -- Tony Toews, Microsoft Access MVP Please respond only in the newsgroups so that others can read the entire thread of messages. Microsoft Access Links, Hints, Tips & Accounting Systems at http://www.granite.ab.ca/accsmstr.htm Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/ |
#28
|
|||
|
|||
COMPILER WRONG !!!
Pacala, did you understand the earlier reference to 'spaghetti
postings'? Your posts tend to be very incomplete fragments, and are exceedingly difficult for anyone out here to make any sense of. It would be very helpful if you could avoid the SHOUTING and provide a beginning - to - end summary in one narrative. I understand that you are hesitant to post your complete code, as it sounds as though it is many thousands of lines in length. Do I understand you to be saying that this code has been running successfully for some time, and then begins to fail after you attempt a (minor) modification and re-compile? After Pseudo-line-edit (Before/After the same) ...it is ALL-OK By this do you mean that you delete the line of code and replace it with the identical code? Or do you mean something else? By ALL-OK, are you saying that you get a run-time error on this line, but after your "Psuedo-line-edit" this line executes without error? How do you know this to be the case? And Problem CODE is always in ANOTHER-Code-Place Are you telling us that your run-time error doesn't always occur at the same place? 1. If you run this code repeatedly (without any alteration at all) does the run-time error stay exactly the same, or does it "move around"? 2. If you add a line of code, delete it, recompile and test what happens? 3. Have you decompiled your mdb? Here is some information on decompiling from Tony Toews: http://www.granite.ab.ca/Access/decompile.htm -- Clif "PACALA_BA" wrote in message ... Hi, In the CODE are NO-PROGRAMMERS-ERRORS (my Opinion) This happens Allways, in 1-2 code-places (most case), sometimes over 10. After Pseudo-line-edit (Before/After the same) ...it is ALL-OK And Problem CODE is allways in ANOTHER-Code-Place BIG-PROBLEM is this wrong-compiler-example Here is the CORE of CODE....or something else missing ? ***************************************** http://i34.tinypic.com/71sdq8.jpg ; I can place the whole code here , but you will see Nothing ....(my Opinion) There must be Something else WRONG... "Tony Toews [MVP]" wrote: PACALA_BA wrote: After Compile is all OK, NO-Errors (But it is NOT REALLY TRUE !!), The compile did compile successfully. But you will still get runtime errors which is what you have. when executing SQL-string , comes an Error: ***Invalid syntax of SQL-String***, because the Acces-System/Compiler DO-NOT see the value of one public constant (=NullSting) !!!!, but in Debugger/Watch IS the value of public constant ANOTHER (="LAB") After 'PSEUDO-LINE-EDIT' (Value before and after the same) it is OK, and runs Error-free over night (15 Hours). Like David said. Post your code. Then we can tell you what the problem is. Tony -- Tony Toews, Microsoft Access MVP Please respond only in the newsgroups so that others can read the entire thread of messages. Microsoft Access Links, Hints, Tips & Accounting Systems at http://www.granite.ab.ca/accsmstr.htm Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/ -- Clif Still learning Access 2003 |
#29
|
|||
|
|||
COMPILER WRONG !!!
=?Utf-8?B?UEFDQUxBX0JB?= wrote
in : Hi, the CODE is SIMPLE My_public_const = "ABC" strSQL = "SOME-STRING" & My_public_const when running.... strSQL = "SOME-STRING" ...**MISSING** My_public_const, WHY ?? Debugger-Watch window.... strSQL = "SOME-STRING" & My_public_const...O.K. -------------- I am building allways the same MDE, with little changes This is allways problem, but allways ANOTHER-CODE-PLACE...!!!??? I have implemented an TEST-RUN, because of this Annoying errors.... If this is the code you have big trouble, because "SOME-STRING" is not valid SQL. your definition of My_public_const = "ABC" is wrong You have defined a variable. Public Const My_public_const = "ABC" If you want REAL help, post the REAL code. If you won't post the real code, go away, You make it impossible for humans to help you. -- Bob Quintal PA is y I've altered my email address. ** Posted from http://www.teranews.com ** |
#30
|
|||
|
|||
COMPILER WRONG !!!
=?Utf-8?B?UEFDQUxBX0JB?= wrote
in : Hi, the CODE is SIMPLE My_public_const = "ABC" strSQL = "SOME-STRING" & My_public_const when running.... strSQL = "SOME-STRING" ...**MISSING** My_public_const, WHY ?? Debugger-Watch window.... strSQL = "SOME-STRING" & My_public_const...O.K. -------------- I am building allways the same MDE, with little changes This is allways problem, but allways ANOTHER-CODE-PLACE...!!!??? I have implemented an TEST-RUN, because of this Annoying errors.... Where is it that your strSQL does not have the value you expect? That is, how are you detecting the "error"? -- David W. Fenton http://www.dfenton.com/ usenet at dfenton dot com http://www.dfenton.com/DFA/ |
Thread Tools | |
Display Modes | |
|
|