>> how does one "prompt" a user for the remaining information for the audit table? Is there a way for stored procedure to do that?

You can't. In most situations SQL Server isn't even running on the machine that the user is sitting at. In this sitution, make the stored procedure accept a parameter for the reason and make sure that the parameter is not optional.

-Mike


>I've been presented with a proposal that will utilize a SQL-Server database. The client desires to have an audit trail of data changes and this must include a "reason for change" that could only be entered by a user. Through a VFP app, no problem as I've already done that. But, it is conceivable that other applications or other users to the database may also have permissions to change data and in that case, we are looking to a generic stored procedure mechanism to update an audit trail table. I suspect I can do that part of it so the real issue becomes how does one "prompt" a user for the remaining information for the audit table? Is there a way for stored procedure to do that?
>
>TIA,
>Steve