WITH OWNERACCESS OPTION Doesn't Work

[DbHd]

I have a multi-user A2k db with both front & backend on a server. Users remote into the server and run it from there.
Users have limited permissions so I include the WITH OWNERACCESS OPTION in my coded queries.

One process calls for deleting data in a temp table but they get an error saying they don't have permissions. They really don't have them in the security settings but I read that the option will override the security settings. If I change the security for those table it all runs ok.

Obviously I can permanently change settings for just those tables, but what gives with the option?

I had originally written the code to create and delete the tables but permissions go in the way there also.

Earle

 

[DbHd]

I've always had excelent response to questions on this forum, so please tell me, is the question stated clearly? Have you experienced this?

Earle

 

[JerryKlmns]

Earle,

I don't know about the problem you are faceing, but if you need to provide some extra permissions functionality to regular users, you could use a more "adminitrative" user [not one of your existing], open a connection with that user and perform actions based on that connection.

BTW, I would strongly recommend to place the FE on every user's PC. That way, the only network traffic is from data travelling around and not from objects (forms, reports etc).

 

[easyit]

I agree with JerryKlmns, you should create a special account which has the apropriate rights. Als indeed you should move the FE to the local drves of your users.

 

[DbHd]

We had it that way for a long time and it wasn't better in our situation. We are a non-profit with very limited funds and most of the PC's were donated and very old with 64Mb ram, and the front end db kept crashing. This way the load moves to the server and does pretty good.

We are beginning to dig out with added memory, upgraded CPUs and the worst PC's changed out for "less worse", but won't go back to putting the front end on user desktops. In fact the long term plan is to rewite the Db into a web based front end and a SQL Db.

Thanks for your help. I did give access to selected tables as a work around but am puzzled about the original issue.