Home |
Search |
Today's Posts |
#1
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
Hello all,
I'm trying to manipulate huge text files (1 - 4 GB each) with the TextStream object. Each file contains 6 months of data...I'm trying to create 6 smaller files with one month of data each. The first step in the process is reading through the whole file one line at a time so I can get a total number of lines (any advice to do this faster/ alternate way would be greatly appreciated...I looked, didn't see a "line count" property of the TextStream or File object so I could avoid reading whole file). This part of the first file (smallest file) took 5 - 10 mins to run. I use the total line count for progress reporting in Excel's progress bar for the next part...building the 6 monthly files from the main file. At some point when the code is running (I don't know what point it is...might change each time code is run), the VBE will no longer let me break into running code ([Ctrl] + [Pause/Break]) for debuging...it just stops running code...it no longer offers me the option to stop or debug. The time before last, I had a breakpoint set just after getting total line count and a "Break when value is true" watch set just a few lines before finishing the first monthly file (roughly 1/6th of the way through the 2nd full read through of the main file) so I could debug the code closing the first monthly file, creating the 2nd monthly file, then continuing to write data. Breakpoint broke into code without problems (VBE not yet tripped up), but "Break..." watch was ignored. This last time running code, it made it through the Total Line Count run through, but threw an error (Data Type mismatch...if I remember correctly). Instead of giving me the option to stop or debug...it just stopped the code...I really need to be able to debug this. XL/VBE goes into "Not Responding" mode (but code is still running) usually when Windows Focus changes to another program. Maybe that is when the VBE trips up and won't let a break-in. Anyone else have issues with this? Is there anything that can be done to fix this (other than staring at XL the whole time code is running hoping a reminder won't pop up to take focus away from XL...hoping XL won't go into "Not Responding" mode)? Is XL 2007's VBE more stable that it will be able to handle this better (I do have XL2007 installed on this machine)? Thanks for any help anyone can provide, CTB |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
Code corrupts file (XL2003) | Excel Programming | |||
Code corrupts file (XL2003) | Excel Programming | |||
XL2003 to XL2000 code converson | Excel Programming | |||
XL2003 VBA: Debuging...can not break or run in break/step mode. | Excel Programming | |||
Running procedures on events xl2003 | Excel Programming |