If you ever decide to make a portable version, let me know

Ugh.

I forgot that I was working with the 13 beta for the past couple of weeks. Everything went fine, nothing to report. I thought I was working with my official 12 version.

But now, they just asked for my license info, because the 14 day trial expired. The older license didn't work, so I exited from 13, and went into the program files folder for version 12.

It gave me multiple error messages, and I eventually tried running it as Administrator. No luck.

So I tried pulling down the official post-beta 13 version. But, my agency has disabled a lot of applications from running (It's not just a matter of changing windows settings), so I wasn't able to install the official version of 13.

However, I was able to reinstall 12. The problem is, the old database definitions are no longer available, so I'll have to re-copy them from Sql Developer and various notes.

So for now, I'll have to continue using 12. If there's some backup folder for the db connection info, can you let me know? Thanks.

Most of the configuration settings including database profiles are store in SQLAssist.sas file. During upgrades a copy of that file is saved with "old" extension. The file content can be completely or piecemeal importaed into the currently running version using the Export//Import button the Options dialog. The file is located in %APPDATA%/Roaming/SSL Assistant/[version] folder. There are different files in version specific folders.

Thanks,

Is it possible it's the files with the .bak extension? I don't see an .old extension in any of the previous versions folders.

There's a sqlassist.ini.bak file which seems to have references to connections, but not actual definitions.

[/img]

.SAS files is what you want there. It looks like you have them available.

I recommend copying that folder (12.x) to a safe place, putting it under version control, and then symlinking it back to its original location. This way you'd have a safety backup in addition to the factory safety backups the setup creates when upgrading. It's also nice to have versions from the past. You can also quickly get your settings when installing/reinstalling it

The SqlAssist.sas is a monster when fighting to handle it as a plain text file. It's particularly nasty when upgrades push settings I've deleted for unused SQL dialects and targets back into the config file, and this causes reordering of the headers of the different settings, also some frequent changes like usage statistics make it constantly change, but IMHO it's still worth the effort. This saved my bacon plenty of times when screwing around with snippets and settings, or simply failing to successfully update due to various reasons (Windows holding some files, required permissions missing, updates/upgrades overwriting/restoring snippets, etc.).

All set, thanks everyone.