D
david
I notice that Vista has a transactional file system (as Novell has/had).
The transactional file system in implemented on and in normal NTFS
using the new Vista NTFS drivers. It's compatible with earlier OS
because earlier OS will just ignore random stuff (uncommitted transactions)
in the file system.
The original purpose of the transactional file system was to handle
installation failures, to enable service packs and updates to be
cleanly rolled back if there was an installation failure.
But it is a general purpose multi-user multi-process transactional
file system, apart from the fact that it also includes registry
transactions.
According to the brief description I saw, it includes transactions on
'blocks' which I assume would be the same as 'pages' in Access.
Has anyone heard of a MS file-system database using this new feature?
What about the new Visual Source Safe drivers? (I ask because I know
they tried to address the problem, I just don't know what they did)
Any suggestion that MS Access ACE will be migrating to the new API?
(david)
The transactional file system in implemented on and in normal NTFS
using the new Vista NTFS drivers. It's compatible with earlier OS
because earlier OS will just ignore random stuff (uncommitted transactions)
in the file system.
The original purpose of the transactional file system was to handle
installation failures, to enable service packs and updates to be
cleanly rolled back if there was an installation failure.
But it is a general purpose multi-user multi-process transactional
file system, apart from the fact that it also includes registry
transactions.
According to the brief description I saw, it includes transactions on
'blocks' which I assume would be the same as 'pages' in Access.
Has anyone heard of a MS file-system database using this new feature?
What about the new Visual Source Safe drivers? (I ask because I know
they tried to address the problem, I just don't know what they did)
Any suggestion that MS Access ACE will be migrating to the new API?
(david)