How to Use SQL View in Access 2007

[jal]

I'm fairly new to Access 2007. In SQL view when I hit F5 to run a query (as we did in Access 2003) it seems to ignore me. So on the menu I've been going to Design > Results > Run and clicking the red exclaimation point labled "Run". I had some luck doing this (as I recall) last week but today it seems to be ignoring me. I don't even get an error message and, as far as I can see, the data isn't updating (it's an UPDATE query).

 

[Banana]

Do you know for fact there are any rows that would be actually updated? I know this is silly question but I've had fallen in that trap thinking something was wrong with my query when in fact it was just because there was no matching rows to update.

What happens if you use View instead?

FWIW, I never really liked the default ribbon so I built my own developer ribbon:
Linky

 

[jal]

Do you know for fact there are any rows that would be actually updated? I know this is silly question but I've had fallen in that trap thinking something was wrong with my query when in fact it was just because there was no matching rows to update.

Thanks for responding. BTW, a while back I created, in VB.Net, a little "SQL View" program for executing queries. When I run the query from my little window it executes fine. So yes, there are rows to be updated and they update fine using my own window. (Maybe I'll upload my little SQL view program sometime).

What happens if you use View instead?

I'll have to find this option - I'm a total newbie at 2007.

FWIW, I never really liked the default ribbon so I built my own developer ribbon:
Linky

Thanks, I'll have to check that out.

 

[Banana]

If my memory serves, in the default ribbon, View is to left of the Run button. That's where you switch between design view, SQL view, and datasheet view. Here, we want to switch to datasheet view and see what happens there.

 

[jal]

Ok, I think I know what the problem was - there was a security banner which I didn't notice in my haste. When I clicked the banner and selected "enable this content" the query started working again.