Do OS make a difference ?

[Trojnfn]

I was on Windows XP and upgraded to Windows 7. Some of my screens do not seem to work now. For example, I have a search screen (continuous form) with a button named btnView. When I click on it, it should pass the id and bring up another form with the detail information for that id. It worked in XP but not it does not do anything in 7. When I click on the button, it just sits there, no errors, nothing.

This is the code for the event procedure for the button.

Private Sub btnView_Click()


DoCmd.OpenForm "Review Shipment Request Form", acNormal, , "ID = " & Me.ID
End Sub

[Robeen]

Have you been able to put a break point on that docmd statement to determine what is actually going on with the "ID = " & Me.ID . . .?
I worked a contract a few years ago where I started out in Access 2007 - XP . . . and then they switched the OS to Win 7 . . . and then they changed the Access version to 2008.
I did run into a few issues [not like what you've outlined above] . . . so I can confirm that there are issues when switching to Win 7.

It always bothers me when something that worked fine in one version - doesn't work when you 'upgrade' !!

[pbaldy]

Another thing to check is that the database is in a trusted location, or code won't run at all. The code you posted should work fine on a Win 7 machine.

Robeen, Access 2008?

[Trojnfn]

Have you been able to put a break point on that docmd statement to determine what is actually going on with the "ID = " & Me.ID . . .?
I worked a contract a few years ago where I started out in Access 2007 - XP . . . and then they switched the OS to Win 7 . . . and then they changed the Access version to 2008.
I did run into a few issues [not like what you've outlined above] . . . so I can confirm that there are issues when switching to Win 7.

It always bothers me when something that worked fine in one version - doesn't work when you 'upgrade' !!

How do I put in a break point (what is that) ? Clicking on the button does not do anything. I made the ID visible so I can see what is being passed and it is the correct id. But the funny thing is that when I open the report manually, the information is there. I just want the report to open when I click on the button, not when I do it manually.

[orange]

For break points and debugging info
see http://www.cpearson.com/excel/debug.htm

Chip deals specifically with Excel but most of the info is applicable to Access.

[The VBA Man]

you should check the button-to-code connection... sometimes that gets broken when you do certain things to the button in design mode... open the form in design mode, click on "btnView", press F4 to bring up the property sheet, and go to the "Event" tab. Under the "On Click" entry, make sure it (still) says "[Event Procedure]"

[Robeen]

Try this:
Add a new button to your Form [Cancel the Command Button Wizard].
With the button selected - go to Property Sheet - Event - and then Click the [...] to the right of the On Click event & select Code Builder.
Put this line of code in there:
DoCmd.OpenForm "Review Shipment Request Form", acNormal, , "ID = " & Me.ID
Run the Form & click the new button & see if the new button works.

Let us know what happens.

[Trojnfn]

Try this:
Add a new button to your Form [Cancel the Command Button Wizard].
With the button selected - go to Property Sheet - Event - and then Click the [...] to the right of the On Click event & select Code Builder.
Put this line of code in there:
DoCmd.OpenForm "Review Shipment Request Form", acNormal, , "ID = " & Me.ID
Run the Form & click the new button & see if the new button works.

Let us know what happens.

I tried that and it did not work, kept getting error about not being able to parse, so I don't know if I did something wrong or typed something incorrectly. However, I did find something out and now it almost works. There is a Securty Warning at the top of the form, saying content has been disabled. I click and then enable (the macros) and now it works. I went to trust center to enable the macros and that seem to do it. But there is another minor problem and I will create a new post.