Report of database object permissions

  • Thread starter Thread starter Guest
  • Start date Start date
Jeff,

I have been off on other things for the past week and am now getting back to
working with your add-in.

This morning I made a new copy of my largest database (the one with about
700 objects) and ran the add-in to transfer the permissions. The progress
bar ran up to 90% and then I got an Error 6: Overflow message. Is there a
limit to the number of objects and/or Usergroups the add-in can handle?

Bruce
 
in message:
Jeff,

I have been off on other things for the past week and am now getting back to
working with your add-in.

This morning I made a new copy of my largest database (the one with about
700 objects) and ran the add-in to transfer the permissions. The progress
bar ran up to 90% and then I got an Error 6: Overflow message. Is there a
limit to the number of objects and/or Usergroups the add-in can handle?
Click to expand...

Hi Bruce,

Humm...that's interesting.
To answer your question, I'm not sure exactly.

The largest file I tested on had around 400 objects and never received a message like that. I will
do some additional testing with larger files and see if I can reproduce the problem.

A couple questions for you if I may. Did you receive the error when the progress bar was at 90% on
the "Exporting" or "Importing" area? Which Access version are you using?

Thanks for the information.
 
The error message came up on the Exporting area.

I am using Windows XP Professional, Version 5.1.2600, Service Pack 2 Build
2600 with Access 2002 (10.6501.6735) SP3.

Bruce
 
in message:
The error message came up on the Exporting area.

I am using Windows XP Professional, Version 5.1.2600, Service Pack 2 Build
2600 with Access 2002 (10.6501.6735) SP3.
Click to expand...

Ok, thanks for the information and feedback Bruce.
I will do some research.
 
Jeff,

I believe I solved my immediate problem using a bit of a work-around.

I made a copy of my original database, and then deleted everything except
the tables and queries. This preserved the permission settings. I then made
another new database by importing the tables/links and queries from the first
new database. I then transferred the permissions for the tables and queries
using the add-in (I got no overflow error messages this time).

In my 2nd new database, I then massaged the permissions for the new objects
(related to our previous discussion). I then imported all of the remaining
objects from the original database file to the 2nd new database file, where
they inherited the permissions I had just established for new objects.

Because I deploy .mde files, my main permission concerns are for the tables
and queries, which transferred over just as I wanted.

The bottom line is that I have successfully created a new, clean database
file and preserved my original permission settings. Not very elegant, but it
worked!

Thanks again.

Bruce
 
Hi Bruce,

A kludgy work-around for sure, but yes that should work.

I've even considered giving an option form that would ask the user
to select which containers of objects they wish to transfer.
Maybe that might solve the issue.

Thanks for the additional information.

--
Jeff Conrad
Access Junkie
Bend, Oregon

in message
 
Back
Top