Bug Report: copy to excel

[ScottMattes]

While comparing output from 2 queries I did a copy to excel. I usually don't use the SQL tab that gets created, but this time I clicked on it and got

"the text string you entered is too long. Reduce the number of characters used or cancel the entry"

When I OK the msg I see that the entire query was on one command (well, at least the first part up to where it exceeded limits).

The problem replicates all the times I tried.

 

[Stew Stryker]

Good one Scott!

I can replicate that easily too, with any query (including header comment) that's longer than 1024 characters. It's clearly an Excel limitation rather than Developer, though I know I've seen longer strings in Excel before.

 

[BWendling]

to solve this (and for better readability) it would be better if the SQL statement was split into one line per Excel row.

 

[ScottMattes]

I almost always enter my SQL as

select field1,
       field2,
       field3
  from table
 where this = 'that'

So I'd like the SQL put into Excel just as entered.

 

[Stew Stryker]

Scott,

I enter my SQL the same way (or at least Beautify it that way).

But I don't see how your statement addresses what I think what BWendling was suggesting; that Developer should output whatever SQL you entered as one line per Excel row, which would break up your sample query above into 5 rows.

Did I misunderstand you?

Personally I would not want the query broken into multiple Excel rows, but I can't say I use this feature all that much! So if it fixed this bug, I'd find a way to live with it.

 

[ScottMattes]

Stew,
I hadn't taken into consideration the one line per excel row, but if I copy the SQL to the clipboard and paste it into excel I get one line per row. I like things to work the same, so doing as BWendling asked would suit me just fine.

 

[rbrooker]

would work for me to, when you want to copy it back, you highlight the column of cells, copy that and it pastes one cell per line, thus you are back with your original sql.