Workgroup File

[Guest]

 

[Guest]

Hi,

I was wondering if I can change the name of an .MDW and if I can how do I
then tell the db what the name is.

The file is on the network with the db however it was named system and I
realize it really shouldn't be.

Please advise.
Thanks!>

 

[Rick Brandt]

I was wondering if I can change the name of an .MDW and if I can how
do I then tell the db what the name is.

The DB does not need to know the name of the mdw file as there is no real
connection between them. What matters is the interanl ID numbers and they
don't change when you change the file name.

 

[Guest]

I have another question after reading a couple of other posts.

I have the db & the .mdw on the same shared drive. However my coworker still
can't get into the database (were still setting stuff up and she's helping me
test). It prompts her to sign in as the user name I created in the workgroup
but it doesn't like her password. Should she be using a shortcut to get the
the files? How do I create the shortcut to the .mdw & .mdb? I saw the syntax
but where does it get typed into?

Thanks for any help you can give me.

 

[Rick Brandt]

I have another question after reading a couple of other posts.

I have the db & the .mdw on the same shared drive. However my
coworker still can't get into the database (were still setting stuff
up and she's helping me test). It prompts her to sign in as the user
name I created in the workgroup but it doesn't like her password.
Should she be using a shortcut to get the the files? How do I create
the shortcut to the .mdw & .mdb? I saw the syntax but where does it
get typed into?

Thanks for any help you can give me.

Being prompted for a login only means that the session being launched is
using a mdw file with a password on the default user "Admin". The login
prompt will always remember the last user name entered so what you are
seeing tells you nothing about the mdw file she is actually using.

You should use the workgroup administrator utility to rejoin her to the
default System.mdw as her default. Then use shortcuts that specify
different mdw files as required. The format for the path, or target for
such a shortcut is...

"Full path to MSAccess.exe" /wrkgrp "Full path to mdw file" "Full path to
MDB"

 

[Guest]

Thanks I appreciate your responses.

I'll play with it and probably have more questions.

Thanks again!

 

[Lynn Trapp]

test). It prompts her to sign in as the user name I created in the

workgroup
but it doesn't like her password.

If she has yet to get logged in, then she doesn't have a password yet. It is
blank.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Big List: www.ltcomputerdesigns.com/JCReferences.html

 

[Guest]

Thanks!

I'll have her delete the password and give it another go.

Thanks again!

 

[Lynn Trapp]

There's no password to delete. She logs in the first time with a blank
password and then she can set her password to anything she wants.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Big List: www.ltcomputerdesigns.com/JCReferences.html

 

[Guest]

I understand. She tried it and it still won't let her in.

What Rick posted about the mdw having a password on the Admin user is correct.

I'm trying to create the shortcut (using the correct mdw) because I don't
want to have to go from workstation to workstation to try to get this stuff
to work. Rick was kind enough to give me the syntax for the shortcut however
I don't know where I (or how to) actually create it in Access. Is there a
window I need to go to?

I'm not a VB person so I'm clueless at this point.

Thanks for your time and patience.'
A

 

[Lynn Trapp]

You need to put the string for the shortcut in the Target field for the
shortcut.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Big List: www.ltcomputerdesigns.com/JCReferences.html

 

[Rick Brandt]

I understand. She tried it and it still won't let her in.

What Rick posted about the mdw having a password on the Admin user is
correct.

I'm trying to create the shortcut (using the correct mdw) because I
don't want to have to go from workstation to workstation to try to
get this stuff to work. Rick was kind enough to give me the syntax
for the shortcut however I don't know where I (or how to) actually
create it in Access. Is there a window I need to go to? [snip]

You don't create the shortcut in Access. A Windows shortcut is a Windows
object that you create in Windows. Right-Click the desktop - New -
Shortcut.

or...

Find MSAccess.exe and drag with the right mouse button to the desktop and
choose "Create Shortcut Here". That will give you a head start as the icon
will already be correct and the target will already have the MSAccess.exe
portion filled in. All you have to do is add the rest.

 

[Guest]

Thanks tons!

I'll be in touch!

I understand. She tried it and it still won't let her in.

What Rick posted about the mdw having a password on the Admin user is
correct.

I'm trying to create the shortcut (using the correct mdw) because I
don't want to have to go from workstation to workstation to try to
get this stuff to work. Rick was kind enough to give me the syntax
for the shortcut however I don't know where I (or how to) actually
create it in Access. Is there a window I need to go to? [snip]

You don't create the shortcut in Access. A Windows shortcut is a Windows
object that you create in Windows. Right-Click the desktop - New -
Shortcut.

or...

Find MSAccess.exe and drag with the right mouse button to the desktop and
choose "Create Shortcut Here". That will give you a head start as the icon
will already be correct and the target will already have the MSAccess.exe
portion filled in. All you have to do is add the rest.

 

[Guest]

Hi Again,

I'm almost there.

I created a shortcut to MSaccess.exe as the following

Target:

"C:\Program Files\Microsoft Office\Office\MSACCESS.EXE" /mbihap "G:\IS\App
Dev & Bus Support\MBI\MBI Shared\Form\SYSTEM.MDW"
"G:\IS\App Dev & Bus Support\MBI\MBI Shared\Form\mbi.mdb"

Start in:

"C:\Program Files\Microsoft Office\Office"

I got the error "The command line you used to start Microsoft Access
contains an option tha Microsoft Access doesn't recognize. Exit & Restart
Microsoft Assess using valid command line options. I click ok 7 times and it
takes me to the .mdw file.

So I went to another post on 04/21/05 - Subject: Workgroup File where the
syntax was described as

"Full path to MSAccess.exe" "path to mdb" /wrkgrp "path to mdw"

Here is the result:

Target:

"C:\Program Files\Microsoft Office\Office\MSACCESS.EXE" "G:\IS\App Dev &
Bus Support\MBI\MBI Shared\Form\mbi.mdb" /mbihap "G:\IS\App Dev & Bus
Support\MBI\MBI Shared\Form\SYSTEM.MDW"

Start in:

"C:\Program Files\Microsoft Office\Office"

I got the same error, clicked ok 7 times and it took me to the mdb.

I changed the start in on both of them to
G:\IS\App Dev & Bus Support\MBI\MBI Shared\Form"
and still got the same error with the shortcut taking me either to the db or
the mdw file which ever was first after the .exe file.

What am I doing wrong?

Thanks for your time!

Thanks tons!

I'll be in touch!

I understand. She tried it and it still won't let her in.

What Rick posted about the mdw having a password on the Admin user is
correct.

I'm trying to create the shortcut (using the correct mdw) because I
don't want to have to go from workstation to workstation to try to
get this stuff to work. Rick was kind enough to give me the syntax
for the shortcut however I don't know where I (or how to) actually
create it in Access. Is there a window I need to go to? [snip]

You don't create the shortcut in Access. A Windows shortcut is a Windows
object that you create in Windows. Right-Click the desktop - New -
Shortcut.

or...

Find MSAccess.exe and drag with the right mouse button to the desktop and
choose "Create Shortcut Here". That will give you a head start as the icon
will already be correct and the target will already have the MSAccess.exe
portion filled in. All you have to do is add the rest.

 

[Lynn Trapp]

What is /mbihap? I think what you want there is /wrkgrp.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Big List: www.ltcomputerdesigns.com/JCReferences.html

Hi Again,

I'm almost there.

I created a shortcut to MSaccess.exe as the following

Target:

"C:\Program Files\Microsoft Office\Office\MSACCESS.EXE" /mbihap "G:\IS\App
Dev & Bus Support\MBI\MBI Shared\Form\SYSTEM.MDW"
"G:\IS\App Dev & Bus Support\MBI\MBI Shared\Form\mbi.mdb"

Start in:

"C:\Program Files\Microsoft Office\Office"

I got the error "The command line you used to start Microsoft Access
contains an option tha Microsoft Access doesn't recognize. Exit & Restart
Microsoft Assess using valid command line options. I click ok 7 times and
it
takes me to the .mdw file.

So I went to another post on 04/21/05 - Subject: Workgroup File where the
syntax was described as

"Full path to MSAccess.exe" "path to mdb" /wrkgrp "path to mdw"

Here is the result:

Target:

"C:\Program Files\Microsoft Office\Office\MSACCESS.EXE" "G:\IS\App Dev &
Bus Support\MBI\MBI Shared\Form\mbi.mdb" /mbihap "G:\IS\App Dev & Bus
Support\MBI\MBI Shared\Form\SYSTEM.MDW"

Start in:

"C:\Program Files\Microsoft Office\Office"

I got the same error, clicked ok 7 times and it took me to the mdb.

I changed the start in on both of them to
G:\IS\App Dev & Bus Support\MBI\MBI Shared\Form"
and still got the same error with the shortcut taking me either to the db
or
the mdw file which ever was first after the .exe file.

What am I doing wrong?

Thanks for your time!

Thanks tons!

I'll be in touch!

anoyse wrote:
I understand. She tried it and it still won't let her in.

What Rick posted about the mdw having a password on the Admin user is
correct.

I'm trying to create the shortcut (using the correct mdw) because I
don't want to have to go from workstation to workstation to try to
get this stuff to work. Rick was kind enough to give me the syntax
for the shortcut however I don't know where I (or how to) actually
create it in Access. Is there a window I need to go to? [snip]

You don't create the shortcut in Access. A Windows shortcut is a
Windows
object that you create in Windows. Right-Click the desktop - New -
Shortcut.

or...

Find MSAccess.exe and drag with the right mouse button to the desktop
and
choose "Create Shortcut Here". That will give you a head start as the
icon
will already be correct and the target will already have the
MSAccess.exe
portion filled in. All you have to do is add the rest.

 

[Guest]

Hi,

Sorry. I thought /wrkgrp represented the name of the workgroup thus /mbihap.
I changed it to /wrkgrp and the error went away. Yeahhhh!

I'm going to send it to my testing partner (who isn't in today) and see what
happens.

I couldn't have done it without either of you!
Thank you so much you guys are great!!

What is /mbihap? I think what you want there is /wrkgrp.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Big List: www.ltcomputerdesigns.com/JCReferences.html

Hi Again,

I'm almost there.

I created a shortcut to MSaccess.exe as the following

Target:

"C:\Program Files\Microsoft Office\Office\MSACCESS.EXE" /mbihap "G:\IS\App
Dev & Bus Support\MBI\MBI Shared\Form\SYSTEM.MDW"
"G:\IS\App Dev & Bus Support\MBI\MBI Shared\Form\mbi.mdb"

Start in:

"C:\Program Files\Microsoft Office\Office"

I got the error "The command line you used to start Microsoft Access
contains an option tha Microsoft Access doesn't recognize. Exit & Restart
Microsoft Assess using valid command line options. I click ok 7 times and
it
takes me to the .mdw file.

So I went to another post on 04/21/05 - Subject: Workgroup File where the
syntax was described as

"Full path to MSAccess.exe" "path to mdb" /wrkgrp "path to mdw"

Here is the result:

Target:

"C:\Program Files\Microsoft Office\Office\MSACCESS.EXE" "G:\IS\App Dev &
Bus Support\MBI\MBI Shared\Form\mbi.mdb" /mbihap "G:\IS\App Dev & Bus
Support\MBI\MBI Shared\Form\SYSTEM.MDW"

Start in:

"C:\Program Files\Microsoft Office\Office"

I got the same error, clicked ok 7 times and it took me to the mdb.

I changed the start in on both of them to
G:\IS\App Dev & Bus Support\MBI\MBI Shared\Form"
and still got the same error with the shortcut taking me either to the db
or
the mdw file which ever was first after the .exe file.

What am I doing wrong?

Thanks for your time!

Thanks tons!

I'll be in touch!

:

anoyse wrote:
I understand. She tried it and it still won't let her in.

What Rick posted about the mdw having a password on the Admin user is
correct.

I'm trying to create the shortcut (using the correct mdw) because I
don't want to have to go from workstation to workstation to try to
get this stuff to work. Rick was kind enough to give me the syntax
for the shortcut however I don't know where I (or how to) actually
create it in Access. Is there a window I need to go to? [snip]

You don't create the shortcut in Access. A Windows shortcut is a
Windows
object that you create in Windows. Right-Click the desktop - New -
Shortcut.

or...

Find MSAccess.exe and drag with the right mouse button to the desktop
and
choose "Create Shortcut Here". That will give you a head start as the
icon
will already be correct and the target will already have the
MSAccess.exe
portion filled in. All you have to do is add the rest.

 

[Lynn Trapp]

I'm glad you got it sorted out.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Big List: www.ltcomputerdesigns.com/JCReferences.html

Hi,

Sorry. I thought /wrkgrp represented the name of the workgroup thus
/mbihap.
I changed it to /wrkgrp and the error went away. Yeahhhh!

I'm going to send it to my testing partner (who isn't in today) and see
what
happens.

I couldn't have done it without either of you!
Thank you so much you guys are great!!

What is /mbihap? I think what you want there is /wrkgrp.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Big List: www.ltcomputerdesigns.com/JCReferences.html

Hi Again,

I'm almost there.

I created a shortcut to MSaccess.exe as the following

Target:

"C:\Program Files\Microsoft Office\Office\MSACCESS.EXE" /mbihap
"G:\IS\App
Dev & Bus Support\MBI\MBI Shared\Form\SYSTEM.MDW"
"G:\IS\App Dev & Bus Support\MBI\MBI Shared\Form\mbi.mdb"

Start in:

"C:\Program Files\Microsoft Office\Office"

I got the error "The command line you used to start Microsoft Access
contains an option tha Microsoft Access doesn't recognize. Exit &
Restart
Microsoft Assess using valid command line options. I click ok 7 times
and
it
takes me to the .mdw file.

So I went to another post on 04/21/05 - Subject: Workgroup File where
the
syntax was described as

"Full path to MSAccess.exe" "path to mdb" /wrkgrp "path to mdw"

Here is the result:

Target:

"C:\Program Files\Microsoft Office\Office\MSACCESS.EXE" "G:\IS\App Dev
&
Bus Support\MBI\MBI Shared\Form\mbi.mdb" /mbihap "G:\IS\App Dev & Bus
Support\MBI\MBI Shared\Form\SYSTEM.MDW"

Start in:

"C:\Program Files\Microsoft Office\Office"

I got the same error, clicked ok 7 times and it took me to the mdb.

I changed the start in on both of them to
G:\IS\App Dev & Bus Support\MBI\MBI Shared\Form"
and still got the same error with the shortcut taking me either to the
db
or
the mdw file which ever was first after the .exe file.

What am I doing wrong?

Thanks for your time!






:

Thanks tons!

I'll be in touch!

:

anoyse wrote:
I understand. She tried it and it still won't let her in.

What Rick posted about the mdw having a password on the Admin user
is
correct.

I'm trying to create the shortcut (using the correct mdw) because
I
don't want to have to go from workstation to workstation to try to
get this stuff to work. Rick was kind enough to give me the syntax
for the shortcut however I don't know where I (or how to) actually
create it in Access. Is there a window I need to go to? [snip]

You don't create the shortcut in Access. A Windows shortcut is a
Windows
object that you create in Windows. Right-Click the desktop - New -
Shortcut.

or...

Find MSAccess.exe and drag with the right mouse button to the
desktop
and
choose "Create Shortcut Here". That will give you a head start as
the
icon
will already be correct and the target will already have the
MSAccess.exe
portion filled in. All you have to do is add the rest.

 

[Guest]

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!

I'm glad you got it sorted out.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Big List: www.ltcomputerdesigns.com/JCReferences.html

Hi,

Sorry. I thought /wrkgrp represented the name of the workgroup thus
/mbihap.
I changed it to /wrkgrp and the error went away. Yeahhhh!

I'm going to send it to my testing partner (who isn't in today) and see
what
happens.

I couldn't have done it without either of you!
Thank you so much you guys are great!!

What is /mbihap? I think what you want there is /wrkgrp.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Big List: www.ltcomputerdesigns.com/JCReferences.html


Hi Again,

I'm almost there.

I created a shortcut to MSaccess.exe as the following

Target:

"C:\Program Files\Microsoft Office\Office\MSACCESS.EXE" /mbihap
"G:\IS\App
Dev & Bus Support\MBI\MBI Shared\Form\SYSTEM.MDW"
"G:\IS\App Dev & Bus Support\MBI\MBI Shared\Form\mbi.mdb"

Start in:

"C:\Program Files\Microsoft Office\Office"

I got the error "The command line you used to start Microsoft Access
contains an option tha Microsoft Access doesn't recognize. Exit &
Restart
Microsoft Assess using valid command line options. I click ok 7 times
and
it
takes me to the .mdw file.

So I went to another post on 04/21/05 - Subject: Workgroup File where
the
syntax was described as

"Full path to MSAccess.exe" "path to mdb" /wrkgrp "path to mdw"

Here is the result:

Target:

"C:\Program Files\Microsoft Office\Office\MSACCESS.EXE" "G:\IS\App Dev
&
Bus Support\MBI\MBI Shared\Form\mbi.mdb" /mbihap "G:\IS\App Dev & Bus
Support\MBI\MBI Shared\Form\SYSTEM.MDW"

Start in:

"C:\Program Files\Microsoft Office\Office"

I got the same error, clicked ok 7 times and it took me to the mdb.

I changed the start in on both of them to
G:\IS\App Dev & Bus Support\MBI\MBI Shared\Form"
and still got the same error with the shortcut taking me either to the
db
or
the mdw file which ever was first after the .exe file.

What am I doing wrong?

Thanks for your time!






:

Thanks tons!

I'll be in touch!

:

anoyse wrote:
I understand. She tried it and it still won't let her in.

What Rick posted about the mdw having a password on the Admin user
is
correct.

I'm trying to create the shortcut (using the correct mdw) because
I
don't want to have to go from workstation to workstation to try to
get this stuff to work. Rick was kind enough to give me the syntax
for the shortcut however I don't know where I (or how to) actually
create it in Access. Is there a window I need to go to? [snip]

You don't create the shortcut in Access. A Windows shortcut is a
Windows
object that you create in Windows. Right-Click the desktop - New -
Shortcut.

or...

Find MSAccess.exe and drag with the right mouse button to the
desktop
and
choose "Create Shortcut Here". That will give you a head start as
the
icon
will already be correct and the target will already have the
MSAccess.exe
portion filled in. All you have to do is add the rest.

 

[Rick Brandt]

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.

 

[Guest]

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.