Thanks Keving, that gets me almost back to perfect. Which other variables can I use instead of

<dbcObjectName>

?

eg. My sales table is named tblSales, which I'm not crazy about but that's what I inherited. I used the BLG to create the business object Sales. I'd prefer the SPs to be named to match the business object: SalesSelect, etc.

Is that possible?

Thanks,

Eric

>>Yes, and I have to change them individually. For example, if I'm in the BLG and I just ran through it to create the business objects for the 'Seminar' table and now I'm creating them for the 'Conference' table, the default stored procedure names will still be 'SeminarSelect,' 'SeminarInsert,' etc. I'll carefully change the first one to 'ConferenceSelect' but the rest don't rename themselves nicely the way the class names did on the previous step.
>>
>>I think this may have changed when I got 3.6, because I thought this actually worked before but I didn't spend enough time in 3.5 to know for sure.
>
>If you put the token

<DbcObjectName>

back into the stored procedure names in the BLG, it automatically places the table from which you are generating stored procedures into the stored procedure name for you. Here are the default values:
>
>

<DbcObjectName>Select
><DbcObjectName>Insert
><DbcObjectName>Update
><DbcObjectName>Delete
><DbcObjectName>SelectByPK

>
>So, for example, if you create stored procedures from a User table, the BLG will name the stored procedures:
>
>

UserSelect
>UserInsert
>UserUpdate
>UserDelete
>UserSelectByPK

>
>You can change the suffix, or even add a prefix, and the BLG will remember your settings the next time around.
>
>Best Regards,