
Signature
Alex Dybenko (MVP)
http://alexdyb.blogspot.com
http://www.PointLtd.com
Thanks, but I already have a utility to install a separate MDE for each user
that is running my app on their desktop. It does the push down of new
release, and kicks users off when BE maintenance is required. I am trying to
find a way not to have to set up a new login/directory on Terminal Services
for each external user. I want to create a guest user login and all external
users will use that login to terminal services. My problem is that on close
of my FE database, I compact. When multiple users are logged onto Terminal
Services in the common directory, and one user exits the application, the
other users who are using the application get a blank screen. The results
are not good. Is there a way to allow users to share an FE database on
Terminal Services. I like compacting on close, but I guess I can take that
out and see what happens??
Thanks,
Karen
>Hi,
>you can install separate FE for each user.
[quoted text clipped - 6 lines]
>> Thanks,
>> Karen
Douglas J. Steele - 09 Mar 2006 23:58 GMT
If you've got multiple users sharing the same front end (which isn't a good
idea, FWIW), then yes, you need to remove the Compact On Close.

Signature
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)
> Thanks, but I already have a utility to install a separate MDE for each
> user
[quoted text clipped - 30 lines]
>>> Thanks,
>>> Karen
Tony Toews - 11 Mar 2006 01:30 GMT
>I like compacting on close, but I guess I can take that
>out and see what happens??
There should be no need to compact on close an FE.
However if your users share an MDE there is a greatly increased risk
of corruption.
Tony

Signature
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm