Re: Probs accessing database for users of newly developed Superuse

Hi Joan,

Sorry for the delay in getting back to you. I wasn't in the office after the
long weekend.

Yes, Startup is set to open the Switchboard form on opening. None of the
options in the Startup dialogue are checked and the menu bar and short cut
menu bar are set to default. I do not have an autoexec macro that runs at
startup.

I think I used the Switchboard manager to create the Switchboard. I say "I
think" because I created the original database about eight years ago and was
away from it for five years. I'm not familiar enough with code to have
written the switchboard's code from scratch; hence, I must have used the
manager. I've included the code for when the form opens below. Its seems
pretty straight forward.

Private Sub Form_Open(Cancel As Integer)
' Minimize the database window and initialize the form.

' Move to the switchboard page that is marked as the default.
Me.Filter = "[ItemNumber] = 0 AND [Argument] = 'Default' "
Me.FilterOn = True

End Sub

Because the startup is prettty straightforward, I would have that if there
was a switchboard problem that problem would exist for all groups. Instead, I
see different problems for users of different groups.

Thanks for your assistance! I really appreciate it.

Chris

"Joan Wild" wrote:

Holding down the shiftkey does not bypass any security permissions, so if
that succeeds, then you don't have a permissions problem with the database
object.

So something in your startup is causing this - from your other post, I'd say
it has to do with the Switchboard and Switchboard Items (I assume you have
startup set to open the Switchboard form on opening).

Check the code behind your opening form, or in an autoexec macro.

What exactly are you doing on starup?

--
Joan Wild
Microsoft Access MVP
"CB" <CB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7E8A70A2-EDAD-4D46-AEA2-43F873B173EA@xxxxxxxxxxxxxxxx
Hi Joan,

I've checked permissions countless times. I've gone so far as to give the
Superuses group full administrative permissions on every single object
including the database - identical settings as the admins group (only as a
test). My Superusers STILL aren't able to log in.

Actually, my Superusers aren't using the database yet. I log in as
administrator and change what I need to change then I log out. I then try
to
log in as one of the Superusers and thats when I have problems.

The weird this is that when I log in in as a Superuser AND hold down the
shift key I can at least enter the database. I can't open tables in any
view
but can create new ones. The queries won't run or open in design view but
they will open in SQL view. Forms won't open in form view but will open in
design view. In this case, each text/comb box has an error (?) and when I
select the '!' I see "Invalid control property: control source" and "No
such
field in the list." If I try to make a new form, I can select a table but
there are no fields available. Reports will open in design view but the
controls have the same error as the ones on the forms. Macros run fine.

Chris


"CB" wrote:

Hi Joan,

Thanks for responding!

The <...> contains the path to the database file, i.e., they don't have
permissions to open the database. Its the same message that would appear
if a
user tried to open the secured database by double-clicking on the file
name.

FWIW, I've asked Chris in another post if it might have something to do
with
the fact that my WIF was created in Access 2000 but I've since updated my
database to A20002-2003. What are your thoughts on that?

Regards,
Chris


"Joan Wild" wrote:

I'm working offline, so can't go to your link, but what does the
message
say? i.e. what is in the <...> part - the database, a
table/query/form?

--
Joan Wild
Microsoft Access MVP
"CB" <CB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:EB773C6C-D244-486B-9F2A-CF27DE9CE468@xxxxxxxxxxxxxxxx
Hi everyone,

I have a split database (Access 2003) that employs USL. Users access
the
database from a shortcut on their desktop. I have been having
problems
when
logged in as a Full-data user that I have not been able to resolve
(see
posting here: http://tinyurl.com/3ljnx3). As a result, I decided to
use
the
Security feature (Tools/Security…) to create a new group called
Superuser.
This group is to have virtually all permissions except administer. I
then
assigned two users to the group.

When I try to log in as one of those two users (using the same
shortcut I
used to change the permissions!), I get the error message “You do not
have
necessary permissions to use <….> object. Have your system
administrator
or
the person who created the object establish appropriate permissions
for
you.”

What gives???? I’m really pulling my hair out between this issue and
my
previous issues (shown in the above link). I really do not want to
add
these
two users to the Admins group but I might have to so I can deploy
this
database to another city (which I need to do fairly soon).

Thanks for any and all help!

Chris





.

Relevant Pages

  • Switchboard does not open when the dbase is opened
    ... You need to open the database in design then go to Tools, ... >database, the switchboard does not open, it opens to the ... >Private Sub Form_Open ...
    (microsoft.public.access.forms)
  • RE: Switchboard Startup
    ... startup the DB sees that a form of that name is already open????) ... Have tried the third option but couldnt open the form from the database ... >> opens the database the default switchboard form opens and then closes itself. ...
    (microsoft.public.access.forms)
  • Re: Probs accessing database for users of newly developed Superuse
    ... "Joan Wild" wrote: ... > I think I used the Switchboard manager to create the Switchboard. ... I've included the code for when the form opens below. ... > ' Minimize the database window and initialize the form. ...
    (microsoft.public.access.security)
  • RE: Compacting MDB help
    ... The autoexec macro opens a ... The FrontEnd.mdb's main switchboard has a cbo to switch back end ... FECompact.mdb runs the few lines of code to compact the FrontEnd.mdb ... I'm quite certain that you can't Compact an open database from within itself ...
    (microsoft.public.access.modulesdaovba)
  • Re: Need code to run on DB close
    ... Initially the Db has the Shift key disabled. ... When someone opens the Db, an AutoExec macro calls a code that validates the ... So the Shift key HAS to be disabled every time the database is closed. ... last form closed then a startup form is perfect for running code ...
    (microsoft.public.access.setupconfig)
Loading