After starting Toad Data Point, the user reports that:
Review of the user’s configuration files confirms that:
This behavior is caused by loss or removal of the user’s local Quest profile configuration, not by a product defect.
Common root causes include:
AppData\Roaming\Quest SoftwareWhen this occurs, Toad Data Point recreates a new empty profile at launch, resulting in no visible connections.
On the affected machine, confirm whether previous configuration data exists:
C:\Users\<WindowsUserID>\AppData\Roaming\Quest Software
Notes:
Locate the Connections file for the active Toad Data Point version (for example, 6.4):
...\Toad Data Point 6.x\Connections.xml
<Connection> entries, the connections are not recoverable from that profileConfirm whether the user is running Toad Data Point in:
If so:
If the original profile cannot be recovered, use one of the following options:
Quest Support can provide step‑by‑step guidance for importing connections if needed.