I have to loop through 342 records in a book. and I am creating new workbooks based on data found in these recs. but not every rec will create a new book. if a book was previously created and subsequent duplicate data is found, the I/O stream will simply add that rec's data to the newly-created book previously. but can anyone here tell me if leaving ''x'' books open for the purpose I described would be a hinderance for the application? I mean, in terms of stack availability and heap issues, I don't think there is any, because books that are opened take no memory other than the mem. space for their object var. and an I/O stream doesn't take anything either. does anyone have any suggestion as to whether that would be a better method than the below code, which I am currently using? I would think that obviously it would be, for obvious reasons. I have a plan already, but I am just looking for input from the real pros that are around here, because I generally don't do this type of work. thanks!
Bookmarks