First, let me state that an Export/Import of Toad settings - or the ability to set a central configuration file, like on a Network Share - is still a highly desirable enhancement.
I’ve finally figured out what the issue is/was:
- Ownership. When copying files from one PC to another - with Windows 7 especially, though it occasionally has been an issue on Windows XP in the past - you may need to ensure that the Ownership of the folders and files that you’re copying is transferred to the user on the Copy-TO machine in order to allow for them to be read and written to properly.
A user with Admin rights on the Target PC must ensure that all sub-folders and files in the C:\Users<target username>\AppData\Roaming\Quest Software\Toad Data Point 3.3\ModuleSettings are owned by the named in the file path.
- Path Name. I’m not sure why the decision was made to hard-code a path in one of the .XML files with TDP 3.3, but that was the issue occurring when I would get the “Failed to load AnalystSettings” error message. In the AnalystSettings.xml file in C:\Users<source username>AppData\Roaming\Quest Software\Toad Data Point 3.3\ModuleSettings the paths to and are hard coded to C:\Users<source username>\AppData\Roaming\Quest Software\Toad Data Point 3.3\Toad Shared and C:\Users<source username>\AppData\Roaming\Quest Software\Toad Data Point 3.3\Toad Projects respectively.
I had to manually edit the file and change the value from what it was on the Source PC to what it is on the Target PC - I would think that it would be preferable to use the Windows Environment Variable of %USERNAME% in order to determine the path, but that may not be supported in the XML configuration.
Since it’s a bit much to ask someone to jump through all of these hoops simply to replicate settings across PC’s - not to mention User Profiles on the same PC - an Export/Import function is far more desirable.