George (and others)
The question and solution raised invites a more general question- Wherever there is a posibility that a table may, over time, grow larger than say some Tens of megabytes, should practices dictate a test for disk space before the SQL. perhaps what I am asking is just a normal practise anyway. What would be the ramifications on overhead if the call for disk space was made before every SQL as one of the ever growing framework components ?
TIA
John Harriss