security and importing queries, forms, etc

[Tim]

How do I change permissions so a non-admin user can import
tables, queries, forms, reports and modules? This all
needs to be done in code with no interaction from the user.

I have a front-end db that is subject to ongoing
development and upgrade whilst live. Each client front-end
has a Version number. When the user logs in, the database
compares the version number to a table on the backend
which lists all the available objects and their individual
version numbers. Any back-end objects with higher version
numbers are selected, the existing object in the front-end
is deleted and the object from the backend is imported.
This all happens invisibly whilst a splash screen is
displayed.

This works fine for Admin users, but regular users do not
have permission to import the objects (or read the custom
datavbase property "Version" that I created). How do I
give them this permission and then remove it once the
update routine is complete?

 

[Joan Wild]

Instead of importing new objects, why not just overwrite the frontend
entirely? There shouldn't be any problems for any user to overwrite their
frontend.

 

[Joan Wild]

Thanks.
Is there any way to do that behind-the-scenes? I can only
think of mailing them a new frontend and asking them to
save it over their old one. I would ratrher not do this as
I have no guarantee that they will do it properly or at
all. Also, there are likely to be quite a few fixes and
updates at first.

You can automate the updating by a batch file. All they'd need to do is
save the frontend to a location on the server (they'd have to save it
somewhere anyway, right?)

Have a look at Tony Toews frontend updater at
http://www.granite.ab.ca/accsmstr.htm

 

[Joan Wild]

I'll try and figure out the updater - as Tony admits, user
documentation is not his strong point. But it looks like
its a utility that each user would run from their own
machine. I'm not able to add/amend the bat that runs when
the PC starts, so I guess I have to rely on the users to
run it themselves when I tell them to.

I just use a batch file. When the application opens, it checks the version
number in the frontend against the version number in the backend (the
version numbers are stored in a table in the frontend, and one in the
backend. If the backend number is higher, Access automatically closes and
runs the batch file, which copies the latest frontend from the server to
their workstation. All they have to do is reopen the application.

Any suggestions as to how I can run a DoCmd from the new
workspace, and therby take advantage of the admin
permissions in the new workspace?

Sorry, I've never attempted this.