Error Msg: Don't have permission to use the object "tmpParametRepo

[Guest]

I am in Office XP with 3 secrity groups. Everything works except the code
(SQL CREATE TABLE ...) in a class module that creates a table to hold
parameters for a report.

I really need to know how to allow the user to create a temporary table,
update it and then delete it in a security group. How do I do this?

 

[Joan Wild]

Instead of creating/deleting a table, you may find it easier to create a
permanent table and append records/delete records from it. If you use RWOP
queries to do this, then users won't even need permission on the table.

 

[Guest]

What happens when I have different users logged on and accessing the same
form and changes the choices he makes on the multilistes? Won't the form
which is created by one, be deleted and changed by the other. I thnk I need
to have a solution where each user creates his own copy of the form. Will
your suggestion do this?

The application is on the server and the client has Access on it by
intranet. When using terminal services, it reacts like there is only one
copy of Access and one user on Terminal Services .

Thanks for your help. I really do not know how to find a solution.

 

[Joan Wild]

Hi Lois,

You should always split a database for multiusers. Put the backend on the
server, and give a copy of the frontend to each user on their workstation.

Since your database is secure, do not use the database splitter as that will
result in an unsecure backend. Instead split it manually. See
http://www.jmwild.com/SplitSecure.htm

If you are using TS, each TS user should have a copy of the frontend in
their own folder. See http://www.granite.ab.ca/access/terminalserver.htm
for more information.

 

[Guest]

The database is split but I have far too many users to put a copy of the
front end on their PC. When there is a change in the application the
maintenance becomes very difficult to keep up. Or is there a fast automated
way of getting them a new copy when it becomes available. Currently, each
user has a shortcut to the same front-end which is on the server.

 

[Joan Wild]

You're asking for trouble having multiple users using the same frontend.

There are a couple of approaches to automating the distribution of a new
frontend.

The following page has a utility you can use
http://www.granite.ab.ca/access/autofe.htm
and also some links to other methods.

 

[Guest]

Thanks for the links. This is what I need.

Seems too bad though since the users will mostly be using the reports so
apart from the form to select the parameters, they are always in Read.

Thanks for the exchange. I won't have thought of this without your help.