Link to home
Start Free TrialLog in
Avatar of aphilips
aphilips

asked on

64k limit in ini file operations?

I'm trying to work with very large ini files and I seem to be hitting some type of limit.  I can't seem to read past a certain point in the files.  Any ideas/workarounds?
Avatar of zsi
zsi

How about using a binary or text datafile instead?  I can understand your interest in using hte ini file for random access (am I correct?).  You can achieve the same functionality by storing your data in a regular text or binary file, reading the entries into a collection, and then accessing the data randomly by its key.  All pretty simple to do and it removes the size limitation that you are experiencing.

Hope this helps!

zsi
Avatar of aphilips

ASKER

No, I'm reading from large ini files... as in cdplayer.ini files that are huge... I'm reading from these ini files and putting it into a Jet db.  I don't need to write to the file, just read.  Short of manually splitting up the file into small chunks, or writing my own access routines, I am stuck.
ASKER CERTIFIED SOLUTION
Avatar of marti
marti

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
aphilips,

The answer that I gave you is still a valid solution.  Just use it for reading the files, since an ini file is just a text file in the first place.  In fact, if all you are doing is transferring the data to a Jet db, then you don't even have to bother with the collections.  Just read each line in and process it out accordingly.

If you email your ini file to me (zsi@aol.com), along with your database file, I'll even write the conversion for you.