Access: Sendkeys and Vista

[John Melbourne]

I am upgrading a long-standing Access application from 97, Xp and a 1280x1024 screen to 2000 ( and eventually 2007), Vista Business and 1280x800. The application has been in frequent use for many years and has several thousand lines of code 'behind' the various forms so that the users do not actually know they are using Access.

At various times I use

Sendkeys "+{Enter}", True 

to force an update of the underlying data tables.

Attempting to run the 97 version under Vista I get >> Run-time error 70 Permission Denied << at the sendkeys line. I have checked that the user has full control permission to all the files involved and also that the various files are not read-only. The problem is presumably Vista related as it works as expected under XP.

[Scott Price]

I am upgrading a long-standing Access application from 97, Xp and a 1280x1024 screen to 2000 ( and eventually 2007), Vista Business and 1280x800. The application has been in frequent use for many years and has several thousand lines of code 'behind' the various forms so that the users do not actually know they are using Access.

At various times I use

Sendkeys "+{Enter}", True 

to force an update of the underlying data tables.

Attempting to run the 97 version under Vista I get >> Run-time error 70 Permission Denied << at the sendkeys line. I have checked that the user has full control permission to all the files involved and also that the various files are not read-only. The problem is presumably Vista related as it works as expected under XP.

I'm not positive about Vista, but I am positive that when eventually landing in Access 2007 you will experience troubles with the SendKeys function. They are part of the disabled-because-of-security-reasons set of very useful functions that will no longer work!

This thread has a few links and suggestions that will be helpful to you:

http://www.thescripts.com/forum/thre...-sendkeys.html

Fortunately there are other ways to do what you are describing.

DoCmd.RunCommand acCmdSave

works, or

If Me.Dirty = True Then  
    Me.Dirty = False 
End If

Regards,
Scott

[FishVal]

Hi, John.

Using SendKeys is not very good habit and practice at all.
There are many other more conventional ways to do the same:

• Form.Refresh method
• Form.Requery method (needs additional coding to return back to the record)
• DoCmd.RunCommand acCmdSaveRecord

[Scott Price]

Beat you to it today Fish! Thanks for your too, though :-)

Regards,
Scott

[John Melbourne]

Scott and Fish

Thanks Guys It's now working

PS Though Scott got in first actually Fish' solution of acCmdSaveRECORD is a more accurate equivalent to +{enter}

[Scott Price]

Scott and Fish

Thanks Guys It's now working

PS Though Scott got in first actually Fish' solution of acCmdSaveRECORD is a more accurate equivalent to +{enter}

You are correct :-) acCmdSaveRecord is the more accurate equivalent.

Glad it's working for you!

Regards,
Scott