Re: Workgroup File

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hi Rick,

I made a copy of the update.mdw (custom workgroup) and placed it out on the
network in the same location as the db. I copied secured path and pasted it
into the Customer shortcut and renamed update.mdw to customer.mdw. See below.

C:\Program Files\MicrosoftOffice\Office\MSACCESS.EXE" "G:\HAP Shared Data\MBI
Projects\request.mdb" /wrkgrp "G:\HAP Shared Data\MBIProjects\customer.MDW"

Then I cleared the password on the Admin user. Now the customers are joining
with the secured .mdw and don't have to log in. Everyone is using the same
..mdw and getting the permissions I gave them (i think).

When I check the permissions using the Customer shortcut it logs me in as
Admin. It's working on our desktops and gives the Admin user the permissions
they should have without them having to log in.

Does this sound like the way I should be setting this up out on the intranet
when it's deployed to the company?

Thanks for your previous response. I really appreciate all of the help this
forum has provided! I wouldn't have gotten this far without your help and
expertise. Thanks again.

"Rick Brandt" wrote:

> anoyse wrote:
> > Hi,
> >
> > It's me again. I'm in the process of deploying the shortcuts on my
> > department's desktops to our Request database.
> >
> > The first shortcut is the MBI Team path - "C:\Program Files\Microsoft
> > Office\Office\MSACCESS.EXE" "G:\HAP Shared Data\MBI
> > Projects\request.mdb" /wrkgrp "G:\HAP Shared Data\MBI
> > Projects\update.MDW"
> >
> > The second shortcut is the Customer path - "C:\Program Files\Microsoft
> > Office\Office\MSACCESS.EXE" "G:\HAP Shared Data\MBI
> > Projects\request.mdb" /wrkgrp "C:\Program Files\Common
> > Files\System\SYSTEM.MDW
> >
> > The problem is that the ADMIN (default user) has the correct
> > permissions when they are using the update.mdw but when they use
> > their system.mdw they can do everything I don't want them to do. I
> > know the reason is because they are using their system.mdw and not
> > the system.mdw on my hard drive. How can I assign permissions for the
> > dafault user (ADMIN) using the customer's system.mdw?
> >
> > Ultimately a link to the db for the customer is going to reside on an
> > intranet webpage and I don't want them to have to login. In other
> > words what I'm trying to do is not have to administer 800+ users
> > (because potentially anyone with Access on their desktop could submit
> > a request) by using permissions assigned to the ADMIN user. Is there
> > anyway to do this? Should I create a system.mdw (customer) and place
> > it in the same location where the db resides? I'm stumped again.
> >
> > You've been a great help in helping my figure this out and I
> > appreciate any input you can give.
> >
> > Thanks and have a good day!
>
> In a setup where you want "normal" users to not have to use your secured
> workgroup file then you have to set the permissions for the user "Admin" and
> for the group "Users" to ONLY be what you want the normal users to have.
> "Admin" cannot have any additional permissions and cannot be listed as the
> owner of the database or any of its objects. I would double-check this last
> one.
>
> Actually if you get this working your people who you want to use System.MDW
> likely don't need a custom shortcut at all. They should be able to have a
> shortcut that points directly at the MDB file as everything else you have in
> their shortcut are the default settings.
>
> On a different note, you should not have everyone opening a common file on
> the network anyway. That will greatly increase the chances that the file
> will become corrupted. The app should be split with each user having their
> own local copy of the front end file.
>
>
> --
> I don't check the Email account attached
> to this message. Send instead to...
> RBrandt at Hunter dot com
>
>
>
.

Relevant Pages

  • Re: Delegating AD Rights (Enable/Disable Accounts)
    ... I will definitely pass it on to my Customer ... user accounts in AD to non-admin staff so that they will be able to ... permissions as Domain User rights will work just fine. ... The UMRA ...
    (microsoft.public.windows.server.scripting)
  • Re: Help! Customer broke OWA access...
    ... I sure hope you are going to charge this customer for his stupid mistake. ... But I did apply the fix after reinstalling SP1. ... >> Microsoft SBS-MVP ... >>> attempting to change permissions to the OWA so that instead of typing ...
    (microsoft.public.windows.server.sbs)
  • RE: How much do you disclose to customers?
    ... our IP's blocked by an IPS or by an unwitting admin. ... from multiple machines has its advantages, especially when given a class C or larger to split up the time. ... Logs are definitly important, one thing I wish automated scanners ... >> I have a question on customer disclosure. ...
    (Pen-Test)
  • Re: Modifying files
    ... > need to protect out software and it's configuration files from our ... ... > customer customer end_user ... these permissions and the role they're intended to play. ... Sounds like you need an installation script, ...
    (comp.os.linux)
  • Re: Problems with Date.toLocaleTimeString
    ... We shipped our software out to a customer that contains a piece of ... var time = date.toLocaleTimeString; ... if they are running the same version of IE as us, why the javascript ... Ask the admin to reinstall the latest JScript engine from ...
    (comp.lang.javascript)