Access 2016 Runtime - support command line ?

syswizard
4StarLounger
Posts: 584
Joined: 12 Jul 2012, 10:34

Access 2016 Runtime - support command line ?

Post by syswizard »

We have a need to run a compact and repair server-side on our LAN using the windows scheduler.
Do we need to purchase an Access 2016 full license or can we invoke command line /COMPACT using the run-time version ?

User avatar
HansV
Administrator
Posts: 78237
Joined: 16 Jan 2010, 00:14
Status: Microsoft MVP
Location: Wageningen, The Netherlands

Re: Access 2016 Runtime - support command line ?

Post by HansV »

As far as I know, /COMPACT should work in Access Runtime.
Best wishes,
Hans

syswizard
4StarLounger
Posts: 584
Joined: 12 Jul 2012, 10:34

Re: Access 2016 Runtime - support command line ?

Post by syswizard »

Thanks Hans. Do you think I'll have any issues with installing the Runtime on Windows Server 2012 ?

User avatar
HansV
Administrator
Posts: 78237
Joined: 16 Jan 2010, 00:14
Status: Microsoft MVP
Location: Wageningen, The Netherlands

Re: Access 2016 Runtime - support command line ?

Post by HansV »

It should work, but you'll have to create a trusted location for the database that you manipulate, otherwise the database won't work correctly.
Since you can't set a trusted location from Access Runtime, you'll have to use a script - see VBScript – Create/Set Trusted Location Using VBScript.
Best wishes,
Hans

User avatar
HansV
Administrator
Posts: 78237
Joined: 16 Jan 2010, 00:14
Status: Microsoft MVP
Location: Wageningen, The Netherlands

Re: Access 2016 Runtime - support command line ?

Post by HansV »

Best wishes,
Hans

syswizard
4StarLounger
Posts: 584
Joined: 12 Jul 2012, 10:34

Re: Access 2016 Runtime - support command line ?

Post by syswizard »

Thanks much Hans...greatly appreciated. That's very slick.

syswizard
4StarLounger
Posts: 584
Joined: 12 Jul 2012, 10:34

Re: Access 2016 Runtime - support command line ?

Post by syswizard »

And....IT WORKS !!
Now we can now run a compact and repair on a daily basis on the Server via the scheduler.
I'm using PowerShell to control the whole process....and to send emails upon failure.