Forcing Users To Update

[JRinderer]

Hello all, I've got a bit of code in Excel I've used to automate opening a website and clicking various objects. I've worked a lot in Excel VBA, but Access VBA is still new, so I've got some of this completed; but I'm having trouble with the last half.

Goals:

1. On opening the Access file I want the program to go to a SharePoint site and check to see that the users file name matches mine.
   1. I have the code to go to the SharePoint site and get the name of the file on SharePoint and then store it into a variable.
   2. I need code to grab the file name of the users application (the Access file).
   3. I know how, in Excel, to write code that will run when the user opens the file

      Workbook_Open()

      ; but I can't figure it out in Access.
2. If the users file name doesn't match mine I want a message box to appear telling the user to download the most recent file. I then want to close the application down
   1. I have code for the message box.
   2. I am still unsure how to reference the Access application itself to close it. Application.close? Can I set an Access object like I can in Excel?

[INDENT=2]
Dim wB as workbookSet[/INDENT]
[INDENT=2]Set Wb = Thisworkbook
Wb.close[/INDENT]

 

[xenou]

Check out creating an AutoExec macro:
https://support.office.com/en-us/ar...database-98BA1508-DCC6-4E0F-9698-A4755E548124
http://www.databasedev.co.uk/autoexec-macro.html

This is one of the cases were we must point out that Access Macros are not simply vba macros but a specific feature in Access that you create using the Macro Designer, not just inserting a module and putting subs or functions in it. Your AutoExec macro can run a vba function in turn, using the RunCode operation.

I would also suggest using a Macro for your shutdown function as well. Just create a macro with a QuitAccess operation. You can call your shutdown macro with vba using DoCmd.RunMacro "MacroName".

I have not personally used AutoExec - I go with another option, which is to create a form, make it hidden, then set it as the startup form for the application. The hidden form then executes the code I want to run in it's open event (including, if you like, starting up another hidden form that has other code in its open event ...). However, I think AutoExec is well known and used successfully so either way is fine.

Note:
I cannot give advice on "forcing" users to do anything, so it is possible that knowledgeable or determined users can bypass these options.