How to prevent a db to beeing virtualized
Ruslan Zasukhin
sunshine at public.kherson.ua
Mon Feb 16 03:48:30 CST 2009
On 2/16/09 10:42 AM, "Tiemo Hollmann TB" <toolbook at kestner.de> wrote:
Hi Tiemo,
> Hello,
> my first experience with valentina on Vista, was that the db was virtualized
> at first access, even though it was read only. I set the db file to write
> protected, and it wasn¹t virtualized any more, logging on with one user.
> BUT logging on with a different user, the db file is virtualized in the user
> profil of the new user and from now on I work with two DBs. How can I prevent
> this behaviour?
>
> Btw. Same seems to happen with SQLite and Rev, see the post ³RE: Where to put
> an ini file on Win with write access for all users? 02-15-09² in RevList
You talk here about strange things...
You say that Vista create for second user ANOTHER copy of files ???
Where is located that file ?
My Documents?
Desktop?
If file is on desktop then I doubt that each user will have "own copy".
Any OS works in this way.
I have never hear that OS have SELF create copies of file for users.
It can give not access yes.
But create copies ...
--
Best regards,
Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc
Valentina - Joining Worlds of Information
http://www.paradigmasoft.com
[I feel the need: the need for speed]
More information about the Valentina
mailing list