Yet another set of questions about split databases

[Larry Kahm]

If this has been answered elsewhere, please point me in the correct
direction.

A database is split: The back-end (BE) resides on a network drive - mapped
to O:\Data\Database Files. The front-end (FE) is still residing on the same
network drive. The application is using a customized MDW for user-level
security.

Questions:

1. Given the current configuration (BE + FE + MDW on server) does a desktop
shortcut need to include the /wrkgrp paramter?
2. When the FE is distributed to each workstation, does the MDW file
continue to reside on the network drive with the BE or does it also go to
the workstation?
3. If the MDW stays on the server, should the desktop shortcut that launches
the application include the /wrkgrp parameter and point to the MDW?
4. If the MDW gets pushed to the workstation, does the desktop shortcut need
the /wrkgrp parm?

Thanks!

Larry Kahm
Heliotropic Systems, Inc.

 

[Allen Browne]

Answers inline.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.

Reply to group, rather than allenbrowne at mvps dot org.

A database is split: The back-end (BE) resides on a network drive -
mapped to O:\Data\Database Files. The front-end (FE) is still residing on
the same network drive. The application is using a customized MDW for
user-level security.

1. Given the current configuration (BE + FE + MDW on server) does a
desktop shortcut need to include the /wrkgrp paramter?

Yes.

BTW, you do have a separate copy of the FE for each user, don't you?
Everyone trying to use the same actual FE file is worse than not splitting
at all.

2. When the FE is distributed to each workstation, does the MDW file
continue to reside on the network drive with the BE or does it also go to
the workstation?

Using a single mdw file on the server means that there is only ONE copy to
keep up to date, e.g. when a password changes.

3. If the MDW stays on the server, should the desktop shortcut that
launches the application include the /wrkgrp parameter and point to the
MDW?
Yes.

4. If the MDW gets pushed to the workstation, does the desktop shortcut
need the /wrkgrp parm?

Yes, but this is not recommended, as you will end up with inconsistent
passwords between the different copies.

 

[Guest]

Answers in-line

If this has been answered elsewhere, please point me in the correct
direction.

A database is split: The back-end (BE) resides on a network drive - mapped
to O:\Data\Database Files. The front-end (FE) is still residing on the same
network drive. The application is using a customized MDW for user-level
security.

Questions:

1. Given the current configuration (BE + FE + MDW on server) does a desktop
shortcut need to include the /wrkgrp paramter?

Yes, unless you join everyone's access to that workgroup which is not good
practice.

2. When the FE is distributed to each workstation, does the MDW file
continue to reside on the network drive with the BE or does it also go to
the workstation?

It should remain on the server. If you distribute it to the workstations,
then whenever there is a change to the groups or users, then you have to
redistribute it. If a user changes there password on one workstation, it
remains the same on all other workstations. If you do have to redistribute
it, and someone did change their password, then it will revert back to what
it was in the copy that you modified.

3. If the MDW stays on the server, should the desktop shortcut that launches
the application include the /wrkgrp parameter and point to the MDW?

Yes, unless you join everyone's access to that workgroup which is not good
practice.

4. If the MDW gets pushed to the workstation, does the desktop shortcut need
the /wrkgrp parm?

Not a good idea. The MDW should reside in the same folder as the BE.