Digital Workshop

Can DW implement new System Variables in the next update for Opus to take into account Windows Vista & Windows 7.

Currently storing or writing data to the applications folder in Windows Program Files folder is difficult and can cause issues under Vista due to virtulisation.

Can DW look into the possibilities of creating a variable for the ProgramData folder in Vista, this would automatically revert back to AppData in Windows XP or earlier.


Also would it be possible to allow the location of a publications Database to be changed, currently I do not think this is possible.

I just want to follow up on this and why I would like to see this implemented very quickly. DW I will pay for this feature alone!

When I create an installer for my publications (I use Pantaray - QSetup) if I select to install into the ProgramData folder called AllUsersAppDataDir in QSetup. The setup will install to the App Data folder in My Documents on Windows 2000/XP but will automatically install this into ProgramData on Vista.

I have tried setting up my software to check the location of the database, but this does not seem possible in Opus. As far as I have tried, it is not possible to change the path of a database in Opus.

This goes back to Vista, I know Microsoft changed a lot for all software developers, but it's been out for over two years now and I would really like this issue addressed soon. If you install your software into the Program Files folder in Windows Vista, Vista does not like you writing to this folder if you're not an admin, and uses virtulisation to protect the OS.

Even using XP, you were never supposed to store data files in the Program Files Folder. Vista has just enforced the rule.
You should be able to use existing functions to achieve what you want to do. See attached.


Paul

Ah yes indeed.

It is possible to do this, but I have been unable to change the path of a database in a publication dynamatically, see thread in Advance on forum. Ideally I would like to be able to change to location of the database based on the version of Windows running.

Releasing a program that hard codes in the path is not ideal either as can cause problems with future edition of Windows. I could just get all the paths and hard code it in, but not ideal.

Thanks for the reply though and the demo app.