You're right, SET BLOCKSIZE is scoped to the datasession, so you'd need to make sure it has been set appropriately.

A stored procedure in a .DBC is just code (like a method or .PRG) so it will run in the current (default) datasession unless you modify it otherwise.

>Thank u for the explanation,
>May I ask u another question ? if so...: If i run the application from an exe file i can set the blocksize to 0 for the session, i suppose, but what happens if i call a stored procedure from an asp application ?
>Does it work if i set the blocksize from the called routine or i should set something elsewhere ?
>Thank u
>Alessio
>>No, the default setting is a relic from the FoxBASE+ days when it yielded a balance between memo file size and disk performance.
>>
>>Setting BLOCKSIZE to 0 has always resulted in the smallest memo files but the tradeoff used to be slower disk performance. With modern disks and OS disk caches it's not an issue any more; in fact, most applications benefit from minimizing total data that must be transferred to or from a disk.
>>
>>>thank u,
>>>i'll try it, i thought that its default setting was the best for saving space...
>>>
>>>
>>>>>I realized that replacing a memo field in a record, the size of the .fpt files grows very much. to reduce it i have to pack it. Is there any other method to do it as i cannot, or better i prefer not to do it, open exclusively the table to run the pack command.
>>>>>thank u
>>>>>Alessio
>>>>
>>>>If it's large now, and you want to shrink it you need to PACK it, which as you note requires exclusive access.
>>>>
>>>>If you want to reduce the memo size and the rate at which it grows you can try SET BLOCKSIZE TO 0. See the help for SET BLOCKSIZE for further information.