@oatleyphotography and what does that mean with respect to your proposed workflow, i.e. having multiple drives all with the assigned letter of P:?
For the location of the database and the cache that will work and you could keep the relevant database and related cache together on a drive designated as P:\ (on Windows only).
For the location of the images the P:\ will simply be ignored and the UUID will be used as I described in the first post I made here Can I use multiple external drives one at a time without conflicts? - #4 by BHAYT. But provided both the drives are not mounted at the same time then the databases (and cache) will relate to the images discovered on that disk.
So, if for P(1) you discover the images on that incarnation of the P:\ drive then the UUID will be for that âversionâ of P:.
If you then replace that drive with P(2) also identifying as P:\ then it will have a different UUID but you will be discovering the images on that version of P:\ and providing you donât somehow get things mixed up then you can have two completely separate environments, what fun!?
So you have on a disk with UUID 0001 (simplified UUID) and configured to have the drive letter of P:\ the database, and cache and images all relate to P(1).
On a disk with UUID 0002 and configured to have the drive letter P:\ when mounted you will have another copy of the database, cache and collection of images all related to P(2)!
You can repeat the exercise with multiple "P:" drives for as many as you feel appropriate.
The major limitation is that you wonât have a database providing a global view of all your images to coral into âProjectsâ and to be searched but that may not be something you want!
PS:- I believe this will work because the parameters for the location of the database and the cache are stored in the configuration file and it uses the drive letter for access and identification.
BUT the config file is one that I know the least about, it certainly contains the âPreferencesâ and it also holds âExport Profilesâ, I believe it also stores the last directory that was being used when DxPL is shut-down.
It is these extraneous bits of data that may or may not lead to issues with the scenario I was âsketchingâ above!?