My stored procedure reverted back -- could Access be the culprit?

[bluegno]

[Note: This pertains to an Access Data Project (ADP).]
I modified a stored procedure on SQL Server, and later discovered that my changes had disappeared. I'm wondering if there's any possiblity that my Access ADP might have been the culprit.

I would think the answer is no. When I open an ADP in design mode, I think of the the top three displayed categories (Tables, Queries and Diagrams) as "windows" (binoculars, whatever) onto SQL Server. My understanding is, ADPs do not directly store any data in these categories.

Since Access lumps stored procedures under "Queries" I would think they would be no exception. The one thing that makes me a bit suspicious is, when I look at the stored procedure from the Access side, it begins with "ALTER PROCEDURE", whereas SQL Server stores it as "CREATE PROCEDURE". I see why it makes sense to implement it this way, but it makes me wonder if Access is actually storing a local version of the script.

Any ideas?

 

[FoFa]

Interesting, did you check the last mod date/time on the SQL server?

 

[bluegno]

I believe I have solved the problem. Turns out to have been a dumb user error (said user having initials YT*).

The code didn't actually disappear; it was never ported to production. Since there was no schema change, I was a bit cavalier about changing the connection string in Access. Forgot about one tiny bit of DATA (procedure text, stored in syscomments) that needed to be ported. Through an odd combination of test oversight and memory juxtaposition, this error was overlooked at release time.

Duh.

*Yours Truly