L
lawwatt
Guest
I am trying to ascertain a way around the folowing, a process which I ran okay under 97. I have an access table, 420,000 records and 34 fields ( about 117M when first populated). two of the fields are initially Null. These fields are then populated based on various tests of the other fields. The problem is that the process of populating these blows the size up to 1.8G - it will compact back.
The population of these fields is accomplished using the table as a DAO recordset, in desperation I am only running a simple do.. loop statement to update the field ( as a test, in real life a lot more complicated).
What is even weirder is that once I have a value in the fields ( and compacted down the database) if I change the value using the same process
a) - with a text string the same size as the one all ready in the field then there is no blowout.
b) - change with a longer string I get the blow out.
While procedurally i can change the order of doing things to avoid this problem in this case I have other processes to run which are similar on similar tables - if not bigger.
Appreciate any suggestions.
The population of these fields is accomplished using the table as a DAO recordset, in desperation I am only running a simple do.. loop statement to update the field ( as a test, in real life a lot more complicated).
What is even weirder is that once I have a value in the fields ( and compacted down the database) if I change the value using the same process
a) - with a text string the same size as the one all ready in the field then there is no blowout.
b) - change with a longer string I get the blow out.
While procedurally i can change the order of doing things to avoid this problem in this case I have other processes to run which are similar on similar tables - if not bigger.
Appreciate any suggestions.
