-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I believe you're confusing replication (publishing) w/ normal FE/BE
deployment.
Normal FE/BE deployment is:
1) Place the data file, BE, in an accessible location (server or
workstation).
2) Ensure the FE linked tables have the correct UNC (Universal Naming
Convention -- \\server\path) to the BE.
3) Distribute a copy of the FE to each user so they can place it on
their PC.
If your set up is: One FE accessed by many users, that is what is
causing the problem. That set up usually corrupts the FE or the data.
If you want to replicate the data (the BE), read the Access Help
articles on Replication. Usually, replicated dbs have both the FE & BE
in one file. The user just synchs w/ the Master BE on a given schedule,
or whenever possible.
If you want to replicate the FE -- most developers shy away from that,
'cuz its easier to just deploy copies of new FEs.
--
MGFoster:::mgf0 0 <at> earthlink <decimal-point> net
Oakland, CA (USA)
-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv
iQA/AwUBQlG4pYechKq OuFEgEQIcQgCggf GzrexQrUA2eYBdJ XiNZx+M7IwAn37S
cBT53uhPfgl44l6 KH+pRW+8i
=/B5n
-----END PGP SIGNATURE-----
Adam Barnett via AccessMonster.c om wrote:
I have an Access application split into a FE and BE with a workgroup file
(.mdw) for authentication. I currently have the FE application setup as a
published application for 40 users. We have been experiencing some unusual
behavior that was not experienced when the application was run in a
client/server environment. What is the proper way to setup an Access
application via published applications? I do not want the user to have to
get to the server desktop prior to launching the app, hence eliminating the
functionality of published applications.