During a programmed export of 1300 record with about 3000 (total) subrecords, the program aborted due to "Client out of memory" about 90% of the way through.

The program is supposed to write the field data to a csv file as it reads through the records. Does this error mean that there is some data that is being 'building up' in memory as it reads through the records?

I thought that data could not be retained between records unless it is written as a static program or in the global values section.

Would adding 'variantname=""' for all variants at the end of the program help to free up memory and avoid this problem?

Thanks

Steve

I'm using SBasic and the progrom is VERY large and quite sloppy becuase i haven't learned how to use subroutines. Its a plain, top to bottom program. I'll email it to you. (There may be about 60 variables assigned)

I looked it over carefully, and dont see where a variable would retain information between records. (I am using no statics or global values) Smaller exports produce perfect .csv's (Thanks Sesame!)

Most variables write to the .csv file and others are used for calculations, etc and all my data in the csv files are correct, so they have to be clearing out after each record (like their supposed to). My guess is I am not using filehandles properly and they are holding in memory as well as writing to disk.

The .csv file is getting to about 7 MB before the client runs out of memory (The process takes about an hour on our 10/100 LAN) the client has 256 MB of memory

I got to 10MB using our server as the client with has 1GB of memory. It crashed but I think becuase another user was working in the same db during the export.

Thanks,
Steve

Erika,

No hurry on looking at my code. I'm doing my export in small batches and its working beautifully. I am always so impressed with sesame once the .csv if complete.


The code exports only the retrieved batch, and the advancing of records is done with programming.  The user does not have to hit the command button on every record.

Should I still consider mass update?

Steve

OK. Sounds like an easier program to write, too.

Thanks for the tip. Always appreciated (and needed).

Again, no hurry on looking at my code, but I'm dying to hear your comments on my export program (it's my 'baby')

Please be gentle with your response.

Thanks,
Steve

Quote:


No, it's not a bug. You are managing your own record navigation, so you have to clear your own variables. You should always initialize variables, even in a Mass Update, which does know how to reset things based on moving between records. Changing the result set position in code does not have the same auto-effects as normal navigation, nor should it. Otherwise, you wouldn't be able to total up all your subrecords, etc.