James,

Thanks for the response.

I have already added the mm_newid to the stored procedures using the method described in the manual. However, my question must not be clear. I want to know if this will only be used via the framework, or if it will be called automatically whenever a table is used and updated. I have another system (non VFP) that will be accessing this same data and I would like to have a standardized method of having the key id updated. However, if this method only works within the framework, I will need to go a different route.

I liken this to what would happen if someone opened a table in VFP that was contained in my DBC. It would automatically call the newid() stored procedure and update the id field.

Based on responses, I'm guessing that this isn't how this works on the SQL server. So, how do I disable the auto ID creation when using the Remote data?

>>I've reviewed the threads and I believe I'm still missing something on this. I am trying to figure out how the mm_newid stored procedure is going to be called when it is not attached to the SQL tables. I went through each step of the "Accessing Remote Data Step-By-Step" and it says to remove the NEWID() reference from all tables, but doesn't say to add the mm_newid() to any tables. Does this mean that mm_newid() is only used programmatically when accessing the SQL tables from within Mere Mortals? If that's the case, I'm going to have to rethink this whole process because we're upgrading to SQL so that other systems will also have access to the tables and be able to add records. I had hoped that the mm_newid stored procedure on the SQL server would have covered for this, but can't seem to figure out how. Maybe I'm missing a step someplace?
>>
>>Any help is appreciated.
>
>You will need to add the mm_newid() stored procedure to the your SQL database. The framework's bizobj is equipped to call that stored procedure to get the newid. Let us know if you need some help creating the stored procedure on the backend.