Security

[Naz]

Hi

I'm trying to secure a run-time database using ULS, but am being told by out
IT department that it may not be possible or at least they don't know how to
do it in a terminal service environment. Does anyone have any idea how to do
that?

As an interim measure to getting ULS up and running is it possible to secure
a database so that people can not link to the data table from say Excel?
Without using ULS or a database password? Hiding the tables doesn't seem to
work.

All help is greatly appreciated.

 

[Rick Brandt]

Hi

I'm trying to secure a run-time database using ULS, but am being told
by out IT department that it may not be possible or at least they
don't know how to do it in a terminal service environment. Does
anyone have any idea how to do that?

Using Terminal Server has absolutely nothing to do with applying ULS. It
might be somewhat awkward to change the default workgroup file for users in
that environment, but almost nobody recommends doing that anyway. If you
give users a shortcut that specifies whcih MDW file to use and which MDB
file to open then ULS will work just fine (at least it will work as well as
it ever does).

As an interim measure to getting ULS up and running is it possible to
secure a database so that people can not link to the data table from
say Excel? Without using ULS or a database password? Hiding the
tables doesn't seem to work.

All help is greatly appreciated.

ULS or a file password (both breakable) are the only ways to do that.