Re: Converting A2K to Access 03

Rick, I'm in the same boat as far as the user not being able to change
the settings. This sounds like a handy work-around. I'll give it a
shot. Thanks much for your time.
Rick Wannall wrote:
In our environment users don't have the abilty to change macro settings or
install things themselves. To get past the prompts you're talking about we
experimented with Certificates, but we could not get them set up properly.
I'm still convinced that certificates are a better answer than this, but to
get around the problem until we can revisit certificates, I use this
vbscript file to open our app:

dim o
set o=createobject ("Access.Application")
o.automationsecurity=1 'set macro security LOW.
o.opencurrentdatabase "\\ourfileserver\files\myappdirectory\myapp.mde"
o.usercontrol=true
set o=nothing

A shortcut on the user's desktop points to the script.

We still have an occasional problem related to some Windows update that does
not accomplish its full mission unless the user can log on to his
workstation as an Admin. The symptom that we get an error message when the
user trys to run the app via the vbscript:

Microsoft Access can't open database because it is missing, or opened
exclusively by another User.

The app is neither missing nor opened exclusively. The cure is to have the
user log out of the workstation, make the user an Admin on his or her own
workstation, have the user log back in. Try once to open the app and get
the same failure again. Try a second time to open the app, this time
successfully. Have the user log out of the workstation. Make the user NOT
an admin on the workstation, and then carry on as usual from then on. If I
remember correctly, the process fixes the problem even for other users,
meaning that if any user goes through the recovery steps I described, then
all users will find that they can open the app from that workstation.

I don't think IT ever found out what part of these updates is not "running
to completion" ( my opinion of the situation) and causing this.

.

Relevant Pages

  • Re: Converting A2K to Access 03
    ... In our environment users don't have the abilty to change macro settings or ... user trys to run the app via the vbscript: ... user log out of the workstation, make the user an Admin on his or her own ... have the user log back in. ...
    (comp.databases.ms-access)
  • Re: Releasing my VB.NET app over the intranet
    ... There are two differences between the simple app and the one I am ... My app uses a DLL that I designed as part of the app. ... workstation, it works fine. ... Settings/sschum/My Documents/Visual Studio ...
    (microsoft.public.dotnet.framework)
  • Program execution question - need guidance
    ... I have written a Windows Forms application in C# that is designed to ... access the program from her workstation. ... No exceptions seem to be thrown. ... The app is basically a database app which displays employee ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: power user logon SBS2003
    ... We only need one computer for the app. ... much about SQL and nothing about MSDE. ... I don't agree that two computers, one SBS and one a workstation, are cheaper ... SBS by itself would have been the cheapest option for us, ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: Compiled .exe file doesnt run
    ... Can you post the code you use to verify a user log in and to call your main ... The code you've listed for the login form's destroy method is completely ... The program runs fine as a VFP app, but not as a standalone .exe app. ... so I compiled the application into an .exe file. ...
    (microsoft.public.fox.programmer.exchange)