Ouch... 90,000 is pushing it. You would have to be very careful not to dump all that info to memory, (start learing how to use seek, tell and $. ).
As for your multiple entries, either check for multiple entries and/or use flock on the file. If you lock the file then only one thing can go in at a time. But like I said.. you might want to have serveral files with the same info (a pseudodatabase) like associate a number to a username in one file and that same number to the address in another file, etc. Someone else might have a better idea how to handle data of that size in an easier way. -----Original Message----- From: Hughes, Andrew [mailto:[EMAIL PROTECTED]] Sent: Friday, February 15, 2002 11:39 AM To: '[EMAIL PROTECTED]' Subject: text file database question I have been given the task to create a contest for which appox. 90,000 people might be signing up(collected info: name, company, email, phone, address1, address2). Due to various reasons, I am not able to use a true database like mySQL to store the information. At this point I am going to have to use a text file, which I have used in the past, but not at this level of possible entries (we are really going to be promoting this heavily on and offline). Please let me know if you think this is a possible dangerous level of entries for a text file. Also, in my experience with text files, I have not been able to stop people from hitting submit a few times before the form submits (i.e. I have multiple lines of the same entry). How would I stop this -- still talking about text files? Thanks, Andrew -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ---------------------------------------------------------------------------- -------------------- The views and opinions expressed in this email message are the sender's own, and do not necessarily represent the views and opinions of Summit Systems Inc. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
