Compiler wrong (02) !!!

Pacala - Do these errors you are continuing to experience occur on
different machines, or are all the (random) errors coming from the same
machine?


"PACALA_BA" <PACALABA.TakeThisOut@discussions.microsoft.com> wrote in message
news:45DCB1A0-AC3A-474C-AD4F-EDACAE3ED404@microsoft.com...
> ACCESS 2003 , WIN XP SP3
> SINGEL USER
> SECURE MDW
> Todays example....
> My_arrray = array("Item0" ,"Item1","Item2","Item3","Item4")
> My_arrray(3) = "" (is empty !!!)
>
> ----------------
> 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/community/en-us/default.mspx?mid=45dcb...-ac3a-4



--
Clif
Still learning Access 2003
 >> Stay informed about: Compiler wrong (02) !!! 

Hi, thank for the Answer.
From same ONE machine (PC-Memory testing OK)
My_arrray(3) = "" ....is empty !!!
but NOT ALLWAYS, only some Versions/builds of My Database
i do not understand such errors....
*********************************************
I have incorporated an TEST-RUN for such errors, but it is inpossible
to check such CRAZY errors....
It is really running OK, but sometimes such problems....


"Clif McIrvin" wrote:

> Pacala - Do these errors you are continuing to experience occur on
> different machines, or are all the (random) errors coming from the same
> machine?
>
>
> "PACALA_BA" <PACALABA.DeleteThis@discussions.microsoft.com> wrote in message
> news:45DCB1A0-AC3A-474C-AD4F-EDACAE3ED404@microsoft.com...
> > ACCESS 2003 , WIN XP SP3
> > SINGEL USER
> > SECURE MDW
> > Todays example....
> > My_arrray = array("Item0" ,"Item1","Item2","Item3","Item4")
> > My_arrray(3) = "" (is empty !!!)
> >
> > ----------------
> > 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/community/en-us/default.mspx?mid=45dcb...-ac3a-4
>
>
>
> --
> Clif
> Still learning Access 2003
>
>
>
>
>
 >> Stay informed about: Compiler wrong (02) !!! 

Hi, thanks for the Answer
Please post full code that demonstrates the error you're talking about...
I am 100 % shure the code is OK
Why:
My_arrray(3) = "" is empty !!!
But NOT ALLWAYS, only some Versions/Builds of my Database....
Build 6.3.2307...wrong
Build 6.3.2308...OK (the same code, nothing changed !!!!)
I can post my code , but it is an LARGE DATABASE
MODULES-size as txt ~5MB

Code lines:
la_RZD_Flds As Variant
la_RZD_Flds = Array("S1", "JJANOXXX", gkII_cKNR, "SJ", "KW", "S", gkII_cIDV,
"MODELL", "FARBA", "S2", "ZP", "OBT", "OBN", "RZD_S", "RZD_N", "Rvs_in_id0",
"Rvs_in_id", "ZP1", "ZP2", "KRC", "FAD", "STAV_X")
when ONE-BUILD was running
Item "FAD" was empty...

"Dirk Goldgar" wrote:

> "PACALA_BA" <PACALABA.RemoveThis@discussions.microsoft.com> wrote in message
> news:45DCB1A0-AC3A-474C-AD4F-EDACAE3ED404@microsoft.com...
> > ACCESS 2003 , WIN XP SP3
> > SINGEL USER
> > SECURE MDW
> > Todays example....
> > My_arrray = array("Item0" ,"Item1","Item2","Item3","Item4")
> > My_arrray(3) = "" (is empty !!!)
>
>
> I don't check you. Here's some test code and results:
>
> '----- start of code -----
> Sub ArrayDemo()
>
> Dim My_array As Variant
> Dim i As Integer
>
> My_array = Array("Item0", "Item1", "Item2", "Item3", "Item4")
>
> For i = LBound(My_array) To UBound(My_array)
> Debug.Print i, My_array(i)
> Next i
>
> End Sub
> '----- end of code -----
>
> And the results printed in the Immediate window are:
>
> 0 Item0
> 1 Item1
> 2 Item2
> 3 Item3
> 4 Item4
>
> Please post full code that demonstrates the error you're talking about.
>
> --
> Dirk Goldgar, MS Access MVP
> www.datagnostics.com
>
> (please reply to the newsgroup)
>
>
 >> Stay informed about: Compiler wrong (02) !!! 

"PACALA_BA" <PACALABA RemoveThis @discussions.microsoft.com> wrote in message
news:DE6E9733-8756-45EE-A85D-C538E7A95031@microsoft.com...
> Hi, thank for the Answer.

You're welcome. I HATE unexplainable errors, myself!

> From same ONE machine (PC-Memory testing OK)

I'ts been several years since I had occasion to do much with PC
diagnostics; but back when I was in a position to deal with possible
hardware failures on a regular basis the ONE fact that came across more
than any other is that 'soft' memory errors are extremely difficult to
pin down.

Not only that, but memory and bus errors both are terrific chameleons --
they more often than not show up as a failure of something else.


Have you tried to duplicate this behavior on a completely different
machine?

--
Clif
 >> Stay informed about: Compiler wrong (02) !!! 

Hi,
another machine: ACCESS XP...similar problems
but it is good idea, i known...
i am now removing colons and multiple 'if' blocks from my
code. (~ 1- 2 weeks)
but i have now very strong feeling that this may be the Problem for
compiler,...
but now only an feeling...
after than i would try it on others machines...
When i create an good Build/Version than runs it NOW over night
~ 15 hours O.K.
Problem is Only CREATING an GOOD Build/Version of MDE Database....

"Clif McIrvin" wrote:

> "PACALA_BA" <PACALABA.TakeThisOut@discussions.microsoft.com> wrote in message
> news:DE6E9733-8756-45EE-A85D-C538E7A95031@microsoft.com...
> > Hi, thank for the Answer.
>
> You're welcome. I HATE unexplainable errors, myself!
>
> > From same ONE machine (PC-Memory testing OK)
>
> I'ts been several years since I had occasion to do much with PC
> diagnostics; but back when I was in a position to deal with possible
> hardware failures on a regular basis the ONE fact that came across more
> than any other is that 'soft' memory errors are extremely difficult to
> pin down.
>
> Not only that, but memory and bus errors both are terrific chameleons --
> they more often than not show up as a failure of something else.
>
>
> Have you tried to duplicate this behavior on a completely different
> machine?
>
> --
> Clif
>
>
>
>
>
 >> Stay informed about: Compiler wrong (02) !!! 

"PACALA_BA" <PACALABA RemoveThis @discussions.microsoft.com> wrote in message
news:1166F6E3-8AFC-40AC-A0B9-A77E11A0FE59@microsoft.com...
> Hi,
> another machine: ACCESS XP...similar problems
> but it is good idea, i known...
> i am now removing colons and multiple 'if' blocks from my
> code. (~ 1- 2 weeks)
> but i have now very strong feeling that this may be the Problem for
> compiler,...
> but now only an feeling...
> after than i would try it on others machines...
> When i create an good Build/Version than runs it NOW over night
> ~ 15 hours O.K.
> Problem is Only CREATING an GOOD Build/Version of MDE Database....
>

I'm happy to hear that it sounds like you're making some progress.

I'm no expert on Access (still fairly new to it, actually) --- I've read
in these newsgroups that obscure 'crud' (maybe not 'corruption' in a
strict sense, but at least extraneous 'junk' that accumulates over time)
is known to sometimes get carried over during an import operation, and
can eventually lead to a corrupted database.

I've also read here of an undocumented "save as text" (( undocumented
[Application.SaveAsText] )) feature that might be of use after you have
finished editing your code. Access MVP Arvin Meyers' Document Database
utility http://www.accessmvp.com/Arvin/Index.htm uses that feature. You
should also be able to search Google Groups and find more discussion of
this feature.

The recent thread in this ng "Risks of decompile" had discussion about
'getting rid of crud.'

HTH!
--
Clif
Still learning Access 2003
 >> Stay informed about: Compiler wrong (02) !!! 

Well, it's empty because you set the value of the array = "". Isn't that what
you did with

My_arrray(3) = "" <<<<<?????

PACALA_BA wrote:
>Todays example....
>My_arrray = array("Item0" ,"Item1","Item2","Item3","Item4")
>My_arrray(3) = "" (is empty !!!)

This problem may be cause by Windows update. Nothing to do with Access. Post
a test code that replicate the error to see whether the problems comes from
PC Hardware or Access. Sometimes you need to declare array variables like..

Dim My_array() As Variant 'with parentheses

instead of

Dim My_array As Variant

Than, remove the parentheses to see that it still works without it.

When you started without the parentheses, it did not work. By adding and
removing the parentheses seems to do the trick.

--
Please Rate the posting if helps you

Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access/200811/1
 >> Stay informed about: Compiler wrong (02) !!! 

"Clif McIrvin" <clare.moe DeleteThis @nevergmail.com.invalid> wrote:

>I'm no expert on Access (still fairly new to it, actually) --- I've read
>in these newsgroups that obscure 'crud' (maybe not 'corruption' in a
>strict sense, but at least extraneous 'junk' that accumulates over time)
>is known to sometimes get carried over during an import operation, and
>can eventually lead to a corrupted database.

I don't know if the crud the decompile removes accumulates until the
MDB is corrupted. That's possible but I don't see any evidence.
Some folks have gone for years without realizing they should be
decompiling on an occasional basis. They report some very dramatic
decrease in MDB sizes and startup times.

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/
 >> Stay informed about: Compiler wrong (02) !!! 

Hi,
undocumented "save as text"..i am using that tool,
but only ~ 5 from ~ 40 builds, are error-free on the first try ...
i run an test-run, to removing PSEUDO-ERRORS..
and that it is O.K.


"Clif McIrvin" wrote:

> "PACALA_BA" <PACALABA.TakeThisOut@discussions.microsoft.com> wrote in message
> news:1166F6E3-8AFC-40AC-A0B9-A77E11A0FE59@microsoft.com...
> > Hi,
> > another machine: ACCESS XP...similar problems
> > but it is good idea, i known...
> > i am now removing colons and multiple 'if' blocks from my
> > code. (~ 1- 2 weeks)
> > but i have now very strong feeling that this may be the Problem for
> > compiler,...
> > but now only an feeling...
> > after than i would try it on others machines...
> > When i create an good Build/Version than runs it NOW over night
> > ~ 15 hours O.K.
> > Problem is Only CREATING an GOOD Build/Version of MDE Database....
> >
>
> I'm happy to hear that it sounds like you're making some progress.
>
> I'm no expert on Access (still fairly new to it, actually) --- I've read
> in these newsgroups that obscure 'crud' (maybe not 'corruption' in a
> strict sense, but at least extraneous 'junk' that accumulates over time)
> is known to sometimes get carried over during an import operation, and
> can eventually lead to a corrupted database.
>
> I've also read here of an undocumented "save as text" (( undocumented
> [Application.SaveAsText] )) feature that might be of use after you have
> finished editing your code. Access MVP Arvin Meyers' Document Database
> utility http://www.accessmvp.com/Arvin/Index.htm uses that feature. You
> should also be able to search Google Groups and find more discussion of
> this feature.
>
> The recent thread in this ng "Risks of decompile" had discussion about
> 'getting rid of crud.'
>
> HTH!
> --
> Clif
> Still learning Access 2003
>
>
>
>
>
 >> Stay informed about: Compiler wrong (02) !!! 

"PACALA_BA" <PACALABA DeleteThis @discussions.microsoft.com> wrote in message
news:9F44BC40-2115-41F9-AC7E-16D0FA20B6D6@microsoft.com...
> Hi,
> undocumented "save as text"..i am using that tool,
> but only ~ 5 from ~ 40 builds, are error-free on the first try ...
> i run an test-run, to removing PSEUDO-ERRORS..
> and that it is O.K.
>
>


Sorry -- your symptoms are beyond my experience.

Speaking for myself, I have noticed a definite change in 'tone' from
your early posts on this topic -- and I definitely thank you for making
that change.

I'd like to encourage you to continue these informative posts as you
work through whatever it is that is causing your problems. From time to
time some of us out here might spot something and be able to offer you a
useful suggestion --- and I'm hoping that when you discover (and share)
the cause and solution to your trouble (we) will ne able to learn from
your experience.

--
Clif
Still learning Access 2003
 >> Stay informed about: Compiler wrong (02) !!! 

Hi
I have SPLIT my Code lines to LENGHT = 80 char
and i see THE CHANGE:
-really fewer CRASHES
- but from time to time are problems present
************************************
- After machine restart i have created on the first time
an MDE database, without Compiler errors and without crashes...
New Access crashes Reported to Microsoft
It seems that LONG lines are NOT FULLY supported by Access-XP/2003



"Tony Toews [MVP]" wrote:

> "Clif McIrvin" <clare.moe RemoveThis @nevergmail.com.invalid> wrote:
>
> >I'm no expert on Access (still fairly new to it, actually) --- I've read
> >in these newsgroups that obscure 'crud' (maybe not 'corruption' in a
> >strict sense, but at least extraneous 'junk' that accumulates over time)
> >is known to sometimes get carried over during an import operation, and
> >can eventually lead to a corrupted database.
>
> I don't know if the crud the decompile removes accumulates until the
> MDB is corrupted. That's possible but I don't see any evidence.
> Some folks have gone for years without realizing they should be
> decompiling on an occasional basis. They report some very dramatic
> decrease in MDB sizes and startup times.
>
> 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/
>
 >> Stay informed about: Compiler wrong (02) !!!