AW: still problems with Vista virtualizing my db

[Tiemo Hollmann TB]

Hello, having analysed it a bit deeper it looks like the behaviour of the db
virtualization depends on the file permission.

 

I removed the write protection of the db file, to be able to update the file

 

I set the file permission of the db file to everyone-readexec

Made a new install of my app with the db - no virtualization

Started my app - the db file is being virtualized immediately with opening
it at prog start.

 

I set the file permission of the db file to everyone-modify

Made a new install of my app with the db - no virtualization

Started my app - no virtualization

Loaded an update for an app file and the db file - no virtualization

Started my App - the db file is being virtualized immediately with opening
it at prog start. The other updated app file is not being virtualized.

>From now on this happens for every user, who opens my app on this machine
and works from now on with an old copy of the db after the next update,
because Vista never updates the virtual store again.

 

Obviously either the rev engine or the valentina engine makes something,
what provokes Vista to virtualize the db. But only after an update???

Any idea?

Thanks

Tiemo

 

 

  _____  

Von: valentina-bounces at lists.macserve.net
[mailto:valentina-bounces at lists.macserve.net] Im Auftrag von Tiemo Hollmann
TB
Gesendet: Donnerstag, 19. Februar 2009 12:07
An: Valentina Liste senden
Betreff: still problems with Vista virtualizing my db

 

Hello,

I still have  troubles with the virtualizing of my db on Vista.

 

First trial was to set the db to write protected. That worked (in my case it
is a read only db) and the db file wasn't put into the virtualStore by Vista
with the first open anymore.

But now I ran into another problem. I have an automatic update procedure for
my app and I can't update my db with a copyfile new to old, because it is
write protected.

 

I think there must be another solution that the db isn't virtualized by
Vista, beside setting it to write protected. If it would be a read/write db
I couldn't set it to write protected either. In a other forum somebody said
that the db engine should handle this Vista issue.

 

Any solution highly appreciated

Tiemo

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.macserve.net/pipermail/valentina/attachments/20090219/343ec51e/attachment.html