Join selections lead to column ambiguity

If I turn off auto add aliases or I elect to delete an alias due to specific preference, the join suggestions break. You can see in the video, it suggests ON Client.ClientID = WorkOrder.ClientID however, when you select it, it drops the table off the left column name:

http://screencast.com/t/mkfiNn46U

If I leave aliases on, this problem seems to not exist, however sometimes I don't want to work with table aliases so I may manually delete them (or turn it off in options) and I get this join suggestion bug.

I get a message about ambiguous column names when trying to execute the code that SQL Assistant puts in.

Using S.A 6.5.278

Am I using this wrong?

This looks like a bug to me. I'm submitting this issue for further investigation.

I was told this issue is fixed in v7 builds. Would you please try beta version 7 and see if it works correctly for you?

	SysOp wrote:
	I was told this issue is fixed in v7 builds. Would you please try beta version 7 and see if it works correctly for you?

I was contemplating it, can I still restore my settings from an exported config file?

	Quote:
	can I still restore my settings from an exported config file?

Sure. The setup should attempt to upgrade your existing file transparently. A new config file will be created in %APPDATA%\SQL Assistant\7 folder. If it fails to that well, you can always use the Import function to load your old settings from 6.5 file from APPDATA%\SQL Assistant\6.5 folder. Please be careful with the import, don't override everything blindly or you would loose some of the new features or make them work incorrectly, so import only the things you want to transfer to v7

SysOp wrote:

	Quote:
	can I still restore my settings from an exported config file?

Sure. The setup should attempt to upgrade your existing file transparently. A new config file will be created in %APPDATA%\SQL Assistant\7 folder. If it fails to that well, you can always use the Import function to load your old settings from 6.5 file from APPDATA%\SQL Assistant\6.5 folder. Please be careful with the import, don't override everything blindly or you would loose some of the new features or make them work incorrectly, so import only the things you want to transfer to v7

It seemed to ignore my config all together. None of my custom snippets or anything else made it over or code formatting rules, history cache settings, etc. All gone.

	Quote:
	It seemed to ignore my config all together. None of my custom snippets or anything else made it over or code formatting rules, history cache settings, etc. All gone.

Would you please email your 6.5 file to support, so that we can try reproducing the file upgrade issue? We need to see why it doesn't recognize your custom changes. Do you know where to find v6.5 config file?

In a mean time, please use the Import/Export button in v7 to load your v6.5 custom snippets and code formatting rules to v7.