Greetings,
I have recently split my DB. Currently, the front-end, back-end, and workgroup files are all on a shared network folder. All of the users are pointed to a single front-end via a shortcut that has the /wrkgrp command switch. This works fine, but I am wanting to make .mde and distribute to each user instead of using a shared .mdb front-end.
Is there any way to tell the .mde file to use the correct .mdw file without using a command switch or manually joining the computer to the workgroup file?
Ultimately, I'd like for each computer to stay connected to the default workgroup file; Each user should have the .mde front-end on their desktops and upon launching, that .mde file should already know the correct workgroup file to use to connect to the back-end. I'd like to avoid having to use a shortcut to launch the .mde if at all possible.
Hopefully that makes sense; thanks in advance for any help you can provide!
~Melagan
______
"It's never too late to become what you might have been.
I have recently split my DB. Currently, the front-end, back-end, and workgroup files are all on a shared network folder. All of the users are pointed to a single front-end via a shortcut that has the /wrkgrp command switch. This works fine, but I am wanting to make .mde and distribute to each user instead of using a shared .mdb front-end.
Is there any way to tell the .mde file to use the correct .mdw file without using a command switch or manually joining the computer to the workgroup file?
Ultimately, I'd like for each computer to stay connected to the default workgroup file; Each user should have the .mde front-end on their desktops and upon launching, that .mde file should already know the correct workgroup file to use to connect to the back-end. I'd like to avoid having to use a shortcut to launch the .mde if at all possible.
Hopefully that makes sense; thanks in advance for any help you can provide!
~Melagan
______
"It's never too late to become what you might have been.