I edit 3.5G files quite frequently. In order to manage them without crashing, I must turn off the Undo capability. Some large files crash upon trying to load, of course, but I frequently go above the 2G file size. Newer versions of TSE use a better Virtual memory system than the older ones did (according the author when I spoke with him on the phone several years ago) and I have had much better luck with large files ever since then. 2G files were the maximum before I upgraded to v4.0b. After that upgrade, I can manage files as big as my system will allow. The files I edit are fixed-length data files. I use TSE to search for data irregularities and duplicate records before I attempt to load these files into a database. The search functions in TSE are still the fastest and best, even with these huge files.
I think the largest I have ever managed is about 4G. At 4G, I am pushing the limits of both physical and virtual memory in a 32 bit system. I have a file that’s 3.6G and another one that is 4.4G currently. I’ll retrieve them from my archive and see if I can load either of them into TSE.
i haven’t gone over 2g, however, very often do similar stuff as Shaun … in particular verifying data layouts, but also too searching for stuff
as he said the search is quite fast … the only time eater is the initial load as i sit & watch the records counter (in the status line) spin rapidly
i run Win 7 64-bit w/ 16gb of ram and all SAS drives
--------------------------------------------------------------
William W. Viergever
Viergever & Associates
Health Data Analysis / Systems Design & Development
2920 Arden Way Suite N
Sacramento, CA 95825
wil...@viergever.net
www.viergever.net
(916) 483-8398
--------------------------------------------------------------