Unable to Allow Full Menu, right click, shortcut menu...

[KT]

I disable the all the options allow full menu, all shortcut menus etc
in startup and then moved my database to a share drive on our network.
Users share this database on the network and I am using the Users and
Groups Permissions to determine what kind of access they get.

I am trying to allow functions that i disable previously like full
menu, shortcut menus, right click. I checked all the boxes in startup
to allow; after restarting the database, i can see the full menu that i
enabled. However, it doesn't work for other users sharing the
database, they still don't get the functions I enabled.

What's going on?

Thanks a million!

Kanley

 

[KT]

BY the way, I tried to hold the shift key while opening the database at
other users' computer, but that doesn't work either..

Please help!!!

 

[Joan Wild]

I disable the all the options allow full menu, all shortcut menus etc
in startup and then moved my database to a share drive on our network.
Users share this database on the network and I am using the Users and
Groups Permissions to determine what kind of access they get.

A bunch of users sharing a single database on a server is not a good idea.
You need to split the database (don't use the splitter wizard, do it
manually); leave the backend (tables) on the server, and give each user a
copy of the frontend (linked to the backend) on their computer.

 

[Joan Wild]

BY the way, I tried to hold the shift key while opening the database
at other users' computer, but that doesn't work either..

Are you holding the shiftkey down long enough? Otherwise, did you disable
the shiftkey bypass (it doesn't sound like it).

 

[KT]

Is that mean I would leave the tables on the server and then send each
of the user a copy of the database with the table linked to the tables
on the server? Will the override or fix the issue of being unable to
right like or see the full menu?

Thanks for your advise!

 

[Joan Wild]

Is that mean I would leave the tables on the server and then send each
of the user a copy of the database with the table linked to the tables
on the server?

Yes. If you think you'll be modifying the frontend often and need to
redistribute it, there are ways to automate this. See
http://www.granite.ab.ca/access/autofe.htm

Will the override or fix the issue of being unable to
right like or see the full menu?

I don't think so. I can't reproduce this problem. It you set the
properties in Tools, Startup, that should do it. Possibly you have changed
the properties on your forms/reports to not allow a shortcut menu?

 

[KT]

I hold the shift key until the database finished opening..should be
long enough. I was able to override the setting with F11 at my
computer, just wasn't able to override the setting with F11 at my
peer's computer.

On the start menu, I did checked the box to allow special key..

headache..

 

[KT]

I found something.

I tried to open the workgroup file (under system 32) in my peer's
computer and then realized that he is not in any of the workgroup, does
that matter? (The shortcut to the database I put on her desktop is
already referring to a workgroup file on the network though)

Second, I found that the MSACCESS.EXE file on her computer can only
open an existing database, but cannot create a new database. I might
not be very clear here, let me know if you dont know what i mean. When
I clicked on the exe file, it said I did not point to any existing
database and asked me to specify a database to open, is that mean
MSACCESS is not installed?

I am lost..

 

[Joan Wild]

I tried to open the workgroup file (under system 32) in my peer's
computer and then realized that he is not in any of the workgroup,
does that matter? (The shortcut to the database I put on her desktop
is already referring to a workgroup file on the network though)

Everything is fine. Even if you don't secure a database, Access still uses
a workgroup file. System.mdw is the workgroup that ships with Access, and
is used for all sessions (unless you specify another one to use, as you've
done with the desktop shortcut).

Second, I found that the MSACCESS.EXE file on her computer can only
open an existing database, but cannot create a new database. I might
not be very clear here, let me know if you dont know what i mean.

Is it possible that she doesn't have Access installed, but instead the
runtime version? What is the error message she gets when she tries to
create a new mdb?

 

[KT]

That could be true. I couldn't find the Access folder under the
Office, neither could i see the access option under the start menu.

I don't think she has an option to create a new mdb, cos whenever I
clicked that MSACCESS.EXE file, an error message popped up and said I
need to point to a specific database, upon clicking OK, Access will
just shut down.

Another problem: (sorry i m creating more...)

I tried to assign her to a workgroup by going to the SYSTEM 32 folder
and join the workgroup. It didn't work of cos, and now, when she tried
to open other databases that she normally didn't need to supply a
password, she is asked for password. I tried to delete the MDW file
she joined, and access won't even open. An error message popped up and
said the workgroup file is needed for startup. My co worker is not
very happy about it at the moment...but i don't know how to restore the
setting for her, which is to withdraw from the workgroup.

 

[Joan Wild]

I tried to assign her to a workgroup by going to the SYSTEM 32 folder
and join the workgroup.

What version of Access? One doesn't just go to the system32 folder and join
a workgroup. What steps did you take?

It didn't work of cos, and now, when she
tried to open other databases that she normally didn't need to supply
a password, she is asked for password.

That's because the workgroup she is joined to by default has a password set
for the Admin User. You could try copying system.mdw from another computer
to her system32 folder.

I tried to delete the MDW file
she joined, and access won't even open. An error message popped up
and said the workgroup file is needed for startup.

As I said in an earlier post, Access always uses a workgroup file, even if
you haven't implemented security.

My co worker is
not very happy about it at the moment...but i don't know how to
restore the setting for her, which is to withdraw from the workgroup.

Actually try copying system.mdw from another computer. Withdrawing from the
workgroup isn't necessarily the answer.

 

[KT]

It's access 97. I went to SYSTEM 32 and used WRKGADM.EXE. When I
first open it, the workgroup administrator name is USER and the Company
and Workgroup field were empty, so I joined the workgroup on the
network for her.

So, to restore the original setting, i need to copy a system.mdw from
another company and paste it back to the system32 folder? After
pasting the file back to the folder, I will need to join this MDW,
right?

Thanks a lot Joan!!

 

[Joan Wild]

It's access 97. I went to SYSTEM 32 and used WRKGADM.EXE. When I
first open it, the workgroup administrator name is USER and the
Company and Workgroup field were empty, so I joined the workgroup on
the network for her.

So, to restore the original setting, i need to copy a system.mdw from
another company and paste it back to the system32 folder? After
pasting the file back to the folder, I will need to join this MDW,
right?

Yes. Be sure you copy system.mdw from a computer that has Access 97 on it.

 

[KT]

By the way, if she only has the runtime version, would that be the
reason why she couldn't do right click or modify my database?

That sounds silly...cos I would think she at least could do right click
or F11 now that I have enable the special keys...

 

[Rick Brandt]

By the way, if she only has the runtime version, would that be the
reason why she couldn't do right click or modify my database?

That sounds silly...cos I would think she at least could do right
click or F11 now that I have enable the special keys...

Doh! _All_ built in menus are unavailable in the runtime. You have to provide
custom ones. It is also impossible to get to the db window in the runtime.

The runtime is strictly for *running* a fully polished and finished application
where all such things are provided by the developer.

 

[KT]

Thank you Everyone, for reading and replying! That might sound silly
but I did learn something thru this silly question...



Kanley

 

[Joan Wild]

Thank you Everyone, for reading and replying! That might sound silly
but I did learn something thru this silly question...

There's nothing silly about learning Kanley.