Maybe, because I never see a problem like that...

Unless the database is broken...

__________________
HTH

Gonzalo

================================================== =========
Read this if you want to know how to get a correct reply for your question.
(Took that from Doug signature and he Took that from Peter profile)
================================================== =========
My programs achieved a new certification :
WORKS ON MY MACHINE
================================================== =========
I know that CVS was evil, and now i got the proof.
================================================== =========

It has nothing to do with datatypes and memory issues are of no concern as it has plenty of it.

Take this line of code which today failed to do what is should:

After executing this line the variable is still empty. Its hilarious and disgusting at the same time.

Access is broken then!. Did you re install it?? Maybe you have to reinstall the whole computer. :(

__________________
HTH

Gonzalo

================================================== =========
Read this if you want to know how to get a correct reply for your question.
(Took that from Doug signature and he Took that from Peter profile)
================================================== =========
My programs achieved a new certification :
WORKS ON MY MACHINE
================================================== =========
I know that CVS was evil, and now i got the proof.
================================================== =========

Memory doesn't have to do with the amount of system resources your PC has, it has to do with the range of memory address space that is reserved when you use each type of variable. For example, Integer variables hold signed 32-bit (4-byte) integers that range in value from -2,147,483,648 through 2,147,483,647. If that value is exceeded, as can be the case with a primary key field, then there is a memory overflow, regardless of how much RAM you have on your computer. It overflowed the reserved address space.

It doesn't seem that the variable types are an issues since strings will hold 2B unicode characters.

That has me stumped. Have you run this on other computers to see if you can duplicate the behavior there? It is very unusual.

__________________
mmcdonal

Look it up at: http://wrox.books24x7.com

I've reinstalled Access on my machine and still have the problems.

There is one work-around which seem to work for me atm. That is exporting all modules to textfiles. Create new mdb on a XP-machine with Office 2003 SP2. Import all objects from the original mdb. Import all VBA modules (the textfiles).

The problem is that i need to do this basically everytime I change something in the code.

fml :-(

Hi
EXACTLY the same on my PCs...
=========================
I have found one one common feature between my and your DB, i do not use
Static Queries. Queries.Count=0
I use dynamically created queries, and Connection/Command.Execute cSQL
-------
keywords: Compiler Wrong , Crazy Error , vba string bug
-------

Have you checked your OPTION EXPLICIT setting?

Have you checked your OPTION EXPLICIT setting?
YES, and All the other Settings
-Decompile: really helps, but the succes is not very High
- Import all into new one from old
- SaveAsText/LoadAsText(MDB-TXT-MDB)
- Acces 2003 reinstall and Last update from WEB
- Ac Help-Detect and Repair, Restore defaults Settings
- Over 1000 Access crashes send to Microsoft in last 2 years
i am Fighting with this ~2 years
--------------------------------------------------------------------------
All the History about ONE CODE LINE !!!
Dim cSQL as String
cSQL = "A" & "B"
-----------------------------
Result SOMETIMES(Random process there ) While running code cSQL = "A"
Result Immediate/Debug Window ***ALLWAYS OK***,cSQL = "AB"
---------
My Opinion Compiler is *** Sometimes *** Wrong
Compile on Demand = OFF (If ON, permanent crash)
I have Large Modules , some over 20 000 lines, But this happens also in small Example DB....
I have some MDE-versions of my DB, they are running dailly (15 hours)...OK,
but before run i MUST it CHECK , for CRAZY ERRORS/VBA STRING BUG...
---------
Keywords: Compiler Wrong/Crazy Error Access/ vba string bug
---------
Example DB AC2002 (ZIP 1,2 MB), an Extraction from Original DB
http://www.dbforums.com/microsoft-ac...xample-db.html
Next week i try to create Example DB for Ac2003
---------
Links to this Problem:
http://sites.google.com/site/pacalaba/

OPTION EXPLICIT , YES
------------
another examples:
-----------
my_Ar = array("a1","a2")
Running: my_ar(1) = Nullstring
Immediate window : my_ar(1) = "a2"
----------
Application.SetOption "Ignore DDE Requests", 0
===============================
Run=> ..........YES Error 2091
? err,err.Description
2091, '' is an invalid name.
Access do NOT see 'Ignore DDE Requests" there !!!!!!!
--------------
RST!My_COL_NAME
--------------
ALLWAYS the same in Immediate/Debug window is O.K.

image-example:
http://i42.tinypic.com/2nun4me.jpg
On the First Time, i do not believe to my eyes....