>
> As far as using NewID(), I decided against it. The hitch was that the invoice number changes depending on which location the user logs in from. Handling this through another object just seemed to be the cleanest way of doing this. I have to make sure this app. can be moved to MSDE, and eventually all the info. consolidated on SQL server so I want to avoid putting too much code in the database.
>
>Thanks for the info.

In that case, you still can accomplish what you are after. After creating a reference to the bizobj, simply call its save method after doing the replace.

loOtherobj = createobj('otherobj')
*-- Pass in some parameters to a custom method
loOtherObj.ReplaceValues('newinvoicenumber')
loOtherObj.save()