Hi,

Sorry to be a broken record, but I've been doing some "destructive testing" of iGrid so that I know what I can and can't do with it.

Today I put in 6 text fields of a page or so long and performed a range of operations on them, mostly filtering and unfiltering according to text contained in the fields. After a few iterations of this I got an "out of stack space" message, Word crashed and will no longer let me access my code, so I have to go back to a backup I saved several hours ago :(

Not backing up often enough is "my bad". But I do need to know how well iGrid (working in conjunction with Word, ADO and Excel) handles large text fields. For the app I am developing, it is possible that there will be several hundred pieces of text of varying length, mostly fairly short but occasionally up to a page or so, with a bunch of additional data fields so that the text can be sorted according to a range of criteria selected by the user.

Are you able to advise me on this?

Also, do you have any suggestions for me (as a newbie, although an old one) as to what (if anything) I can do to reduce the chance of "out of stack space" crashes happening again?

Thanks again,

Ian

Today I put in 6 text fields of a page or so long and performed a range of operations on them, mostly filtering and unfiltering according to text contained in the fields. After a few iterations of this I got an "out of stack space" message, Word crashed and will no longer let me access my code

No problem to bombard us with your questions - we are ready to examine every iGrid issue and fix the problem if it is on our side.

But are you sure the problem you are describing is an iGrid problem? If so, send us please a demonstration we can launch on our pc to reproduce the problem and debug it.

As for iGrid limitations, every iGrid cell allows you to store and edit a string of up to 4'294'967'295 characters on WinNT systems.