With SCATTER NAME, you can create an object that has one property for each field. Perhaps you can pass this object as a parameter.
>Hello,
>
>We are experiencing the following problem with the VFP limit that a procedure can only have a maximum of 26 parameters :
>
>We are using VFP as front end and a VFP database as back end, but with a custom middle tier based on ADO, which should allow to switch to an Oracle back end with the least possible work. We decided that every access or modification of the database should be done through stored procedures, thus isolating the code to rewrite when switching to Oracle.
>
>A problem arose very quickly when I tried to write a procedure to insert in a table with 60+ field, because a VFP stored procedure cannot handle that many parameters.
>
>Does anybody have a workaround ? I tried to think about one without success. It would be nice to use an object reference or array instead of single-value parameters, but I don't think that ADO would handle those.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)