View Issue Details

This bug affects 1 person(s).
 8
IDProjectCategoryView StatusLast Update
04361Bug reportsImport/Exportpublic2010-06-08 21:51
ReporterGill Assigned Toc_schmitz  
PrioritynormalSeveritypartial_block 
Status closedResolutionunable to reproduce 
Product Version1.90b 
Summary04361: Export token field problem
Description

[Microsoft][ODBC SQL Server Driver][SQL Server]Ambiguous column name 'token'.:SELECT [id], [lastpage], [startlanguage], [token], [datestamp], [startdate], [ipaddr], [refurl], [77379X2X2SQ001], [77379X2X2SQ001comment], [77379X2X2SQ002], [77379X2X2SQ002comment], [77379X2X2SQ003], [77379X2X2SQ003comment], [77379X2X3121], [77379X2X3122], [77379X2X4131], [77379X2X4132], [77379X2X5], [77379X3X19], [77379X3X6], [77379X3X7], [77379X3X8], [77379X3X8comment], [77379X3X9241], [77379X3X9242], [77379X3X9243], [77379X3X9244], [77379X3X9245], [77379X4X10311], [77379X4X10311comment], [77379X4X10312], [77379X4X10312comment], [77379X4X10313], [77379X4X10313comment], [77379X4X10314], [77379X4X10314comment], [77379X4X10315], [77379X4X10315comment], [77379X4X10316], [77379X4X10316comment], [77379X4X11], [77379X4X11comment], [77379X4X12], [77379X5X13], [77379X5X13comment], [77379X5X14], [77379X6X151], [77379X6X152], [77379X6X153], [77379X6X154], [77379X6X155], [77379X6X156], [77379X6X16], [77379X6X17] FROM survey_77379 LEFT OUTER JOIN tokens_77379 ON survey_77379.token = tokens_77379.token ORDER BY id

Steps To Reproduce

Exporting results from survey produces the above message if I select token field to export. The token field appears in both joined tables, and SQL cannot tell which one to select.

TagsNo tags attached.
Bug heat8
Complete LimeSurvey version number (& build)8691
I will donate to the project if issue is resolved
BrowserChrome
Database type & versionSQL Express 2008
Server OS (if known)Server 2008
Webserver software & version (if known)IIS7
PHP Version5.? (most recent)

Relationships

duplicate of 04334 closedmachaven Export to Word document fails 

Users monitoring this issue

There are no users monitoring this issue.

Activities

Mazi

Mazi

2010-05-26 14:07

updater   ~11970

Can you please test if the problem still exists at the latest 1.90beta3?

lemeur

lemeur

2010-06-04 22:26

developer   ~12181

@Gill, can you give feedback on hhow 1.90beta works for you ?

Mazi

Mazi

2010-06-05 12:37

updater   ~12185

Carsten, you fixed several MS SQL errors recently and are the only developer having MS SQL installed. Can you check?

c_schmitz

c_schmitz

2010-06-05 15:57

administrator   ~12187

To me it looks like this is already fixed in b3.

Gill

Gill

2010-06-05 16:07

reporter   ~12188

Please accept profuse apologies. Have not been able to install the upgrade - away from office for some time. Will try this on return.

Issue History

Date Modified Username Field Change
2010-05-21 15:33 Gill New Issue
2010-05-21 15:33 Gill Status new => assigned
2010-05-21 15:33 Gill Assigned To => user372
2010-05-26 14:06 Mazi Assigned To user372 => Mazi
2010-05-26 14:07 Mazi Note Added: 11970
2010-05-26 14:07 Mazi Status assigned => feedback
2010-06-04 22:26 lemeur Note Added: 12181
2010-06-05 12:37 Mazi Assigned To Mazi => c_schmitz
2010-06-05 12:37 Mazi Status feedback => assigned
2010-06-05 12:37 Mazi Note Added: 12185
2010-06-05 15:57 c_schmitz Note Added: 12187
2010-06-05 15:57 c_schmitz Status assigned => resolved
2010-06-05 15:57 c_schmitz Resolution open => unable to reproduce
2010-06-05 16:05 c_schmitz Relationship added duplicate of 04334
2010-06-05 16:07 Gill Note Added: 12188
2010-06-08 21:51 c_schmitz Status resolved => closed