Hiding Working File

[Ripper]

Is there a way to hide the file that is created when the backend of the data
base starts? I have the properties of the backend hidden so that unless you
have your computer set up to see hidden files, you can't. My students keep
thinking it is funny to delete the working file and therefore I would like to
hide it.

 

[John Vinson]

Is there a way to hide the file that is created when the backend of the data
base starts? I have the properties of the backend hidden so that unless you
have your computer set up to see hidden files, you can't. My students keep
thinking it is funny to delete the working file and therefore I would like to
hide it.

They might find it a bit less amusing if the consequence was that they
are obliged to recreate it from scratch or else get an F.

John W. Vinson[MVP]

 

[Smartin]

Is there a way to hide the file that is created when the backend of the data
base starts? I have the properties of the backend hidden so that unless you
have your computer set up to see hidden files, you can't. My students keep
thinking it is funny to delete the working file and therefore I would like to
hide it.

As you have "seen" you can't really hide the file. If you are in an XP
and/or networked environment you can place the BE in a folder where the
students do not have rights to delete files.

Thinking further upstream ... you haven't said how old these students
are. If they are old enough to understand the concept of an acceptable
use policy (AUP) and the consequences of breaking said policy, that
might set their behavior straight.

 

[John Vinson]

As you have "seen" you can't really hide the file. If you are in an XP
and/or networked environment you can place the BE in a folder where the
students do not have rights to delete files.

That will cause problems, though, in a multiuser application: the
users must have the privileges to create and delete files, because of
the .ldb file that Access automatically creates and deletes.

John W. Vinson[MVP]

 

[Smartin]

That will cause problems, though, in a multiuser application: the
users must have the privileges to create and delete files, because of
the .ldb file that Access automatically creates and deletes.

John W. Vinson[MVP]

Duh me! How easily I forget. In that case, I rest on my second
proposition. Thanks John.