>>>Can I use the INSERT INTO .. FROM MEMVAR and
>>>get the proper next primary key as employed in the
>>>Tastrade app? The nextid routine works via the
>>>INSERT INTO .. VALUES but not from MEMVAR.
>>>The uniqueness of the PK is violated that way. I prefer
>>>the FROM MEMVAR technique but will have to try
>>>something else unless there is a workaround...
>>
>>It doesn't matter how you insert a record, but it matters what values you are going to use. I believe, that Tastrade uses PK-generated stored procedure value as default, and doesn't include this field in INSERT .... VALUES() list. I guess you can imitate the same thing with MEMVAR but you will have to specify that primary key field will not be included in the list.
>
>Guess I don't know how to exclude just one field from a MEMVAR list. That
>is why I am having the trouble I am having...

I guess (personally I don't use MEMVAR), that it would be enough to release m.ID (if 'ID' is primary key field) right before INSERT. Also, INSERT command syntax allows you to include literal list of fields to be inserted.