>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?
>

The mm_newid stored procedure is not called automatically whenever you add a new record to the table. It is called by the framework. There is an option to not pre-fetch the primary key. In a remote database, that would be akin to not populating your primary key. If you choose to use an identity column as your promary key, this would be the solution you are looking for. Otherwise, you would need to define an insert trigger to call mm_newid to populate that value. Does that answer your question?