Feedback by UserVoice

Futski

My feedback

  1. 3,380 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    I’m happy to let you know that we are in the planning stages to make Excel for Windows scroll without jumping to the edge of the cell so you’ll be able to scroll smoothly. We don’t yet have a target date, but wanted to tell you about our plans.

    We appreciate all the votes and comments supporting this suggestion.

    Thanks – Steve K [Excel]

    An error occurred while saving the comment
    Futski commented  · 

    @ROBERT LACKOWSKI - I agree with you. And while it is outside the scope of this topic, it would be great to have just a sliver of gray spaces to show the borders of cells in the top most visible row and left most visible column. Maybe not even gray space, just display the cell borders. Can't count how many times I've wanted to see that.

    An error occurred while saving the comment
    Futski commented  · 

    @Anonymous, You can already set how many rows to scroll per scroll tick. This is actually a Windows system setting.
    1) Settings / Devices / Mouse
    2) Roll Mouse Wheel = Multiple Lines at a time
    3) Adjust the Choose how many lines to scroll slider

    An error occurred while saving the comment
    Futski commented  · 

    @I got a headache - Yep, I think you're right. Forgot about that. :-D

    An error occurred while saving the comment
    Futski commented  · 

    WOW. MS is on a roll. So far I've seen 3 updates today.
    1) "Not at this time" for Conditional Formatting - Apply to named ranges
    2) "Accepting Votes" for Add Center Across Selection
    3) "Planned" for Scroll Better.

    What a day. Never saw more that the sporadic update in the past.

    An error occurred while saving the comment
    Futski commented  · 

    Robert, I like your solution. :-)
    We can only hope that MS sees these "Constructive" suggestions and acts on them.

    An error occurred while saving the comment
    Futski commented  · 

    So the big question is "Is Smooth Scrolling really an OS issue?". And that is a definitive Yes and No.

    It's "Yes" because:
    There are some OS level Mouse scrolling options that do control how Excel and other applications scroll. In Win 10, see Control Panel / Mouse / Roll Mouse wheel to scroll x lines at a time. Here you can tell the OS to scroll 1 line or 3 lines or 100 lines (or any number of lines in between). You can also tell it to scroll 1 "Screen" at a time. An Excel row is considered to be a line and it honors this scroll options set on the Mouse setting page.
    Windows created this to provide a unified "Windows Experience"that applications can all follow to provide a consistent feel within windows. Unfortunately there is no option for smooth scrolling. By default this option is set to scroll 3 lines. Setting it to 1 line might be helpful but that will also affect scrolling in other applications including web browsers.

    So why then do some some browsers have smooth scrolling? Some browsers have their own display engines that optionally, natively support smooth scrolling. Other browsers have extensions that allow the smooth scrolling. But the bottom line is that the Browsers have their own display engines that 1) are set to provide smooth scrolling, or 2) Look up the "Lines to Scroll" value from the OS and scroll based on that. Excel for the Web is essentially a Web application, so it's scrolling follows the Web browsers scrolling.

    Here's a few links for more info:
    https://superuser.com/questions/956381/no-smooth-scrolling-on-windows-10
    https://blogs.windows.com/msedgedev/2020/04/02/scrolling-personality-improvements/

    It's "No" because:
    The OS has no context as to the actual data that Excel needs to display. Excel controls what gets displayed and how far to scroll with eace detent of the mouse scroll. Excel may send the data to the OS for "actual" display, but Excel is still in control for "what" to display. When Excel sees a scroll wheel event, it updates what to be display by looking at the Windows Scroll option and adjusting accordingly.

    The fix:
    I see the fix as one of two possibilities
    1) Build it's own display engine that completely ignores the windows scroll options. The downside being that Excel would no longer follow the "Windows Experience" scrolling.
    2) A two prong approach to allow a unified "Windows Experience". First, Windows needs to add a "Smooth Scrolling" option to the mouse scrolling options. Second, Excel needs to be modified to support the new Windows Smooth Scrolling option. The problem with this is that other applications would also need to be modified to support smooth scrolling.

    So there you have it. You can make up your own mind as to whether or not the OS needs to be fixed or Excel needs to be fixed. Either way doesn't matter. Bottom line is we need smooth scrolling.

    An error occurred while saving the comment
    Futski commented  · 

    The sad part is that MS probably looks at 3,100+ votes as a mere pittance compared to the total Excel user population. Little do they realize that there are probably millions of other users just as annoyed by cell snapping as the 3,100+ votes here. Those other millions of users simply haven't found this page and voted.

    MS would do well for itself if they looked at UserVoice and it's userbase as as being the most passionate, skilled and demanding of it's Excel users. Satisfy the UserVoice userbase and millions of other users would both benifit and be much happier as a result.

    But alas, that'll never happen!!!! :(

    An error occurred while saving the comment
    Futski commented  · 

    @anonymous, sarcasm is definitely your strong suit.
    My bet is now that Eric is the Principal Program Manager, ALL useful and needed suggestions, be it Excel or otherwise, will wither away in the depth's of despair, never to see the light of day.
    I'd say this is a big loss for all of us, but you can't lose something you never really had. Our loss just got deeper and darker.

    An error occurred while saving the comment
    Futski commented  · 

    @Anonyomous, Been there, done that, a thousand times. But why should I be forced into some crazy work-around when Excel should just be able to handle it.

    Let's remember, there is a completely different and popular UserVoice forum dedicated to data import. So lets not turn this topic into a discussion about CSV's.

    An error occurred while saving the comment
    Futski commented  · 

    It is clear that MS would rather focus on fancy new features than make our lives easier with what we already have. Some of the new features like xLookup and Spill features are truly impressive indeed.

    But I'd be much happier if MS would just step away from the new features for a year and focus on fixing all these little irritants that make our lives more difficult.
    1) Fix Smooth scrolling
    2) Allow us to enter table columns in Conditional Rules "Applies To" box, and the rule formula too.
    3) Stop making a mess of the conditional rules every time a person copies/pastes a cell, especially in a "Table".
    4) Make all those fixed size dialog boxes re-sizable so we can more easily enter longer formulas or data ranges.
    5) Give us option to select a default paste type - ie. Paste values only, or paste with formatting
    6) Fix your CSV import process so we can include numeric data with leading zeros. Sometimes we need the leading zeros.
    7) Stop assuming our long numbers want to be formatted as Sci. Notation.
    8) Bring back MDI as a configurable option for those of use that actually like it.
    The list goes on and on....

    It's time MS stopped trying to woo us with fancy new features and instead, fix the existing problems.
    You can put lipstick on a pig, but in the end, it's still a pig.

    An error occurred while saving the comment
    Futski commented  · 

    @PN. That is truly an excellent video explaining the smooth scrolling issue. Well Done !!!
    I can only hope that MS will understand the problem after seeing this.

    An error occurred while saving the comment
    Futski commented  · 

    @Roy, I stand corrected. "Famous" is definitely what I meant. Didn't mean to disrespect Col. Potter. :)

    An error occurred while saving the comment
    Futski commented  · 

    @Anonymous, Sorry but in the infamous words of Col. Sherman T Potter, "Horse Hockey!" Every other app in Windows is capable of smooth scrolling. The cell scrolling is a "feature" of Excel. In fact Excel can smooth scroll. Just grab the scroll bar, slide it around and see the smooth scrolling. MS just doesn't want to rewrite the Excel scrolling routines to better support smooth scrolling with the arrow keys. I'm betting they just don't see that as a "Value Added" feature. They'd much rather spend their time building something fancy and new that will affect far fewer people than smooth scrolling would.

    An error occurred while saving the comment
    Futski commented  · 

    I've seen many people claim that cell scrolling is an OS feature, and not an Excel issue. Sorry but I don't buy that for a second. Almost every other application that needs scrolling uses smooth scrolling. When was the last time you saw IE using cell scrolling? Uh never.... In addition, Excel already "kind of" supports smooth scrolling, Grab the slider on the scroll bar, you can move the screen to half way through a cell. Or try clicking the mouse wheel button. Smooth scrolling supported there too. But both of these are half @$$ solutions to smooth scrolling, but prove that Excel can do it.
    So the big question is why doesn't MS finish implementing smooth scrolling using the arrow keys too. And maybe provide us some control over smooth / cell scrolling.

    I think MS is too busy trying to add fancy new features that only relatively few users will use, rather than fix the many issues to make existing users happy. MS just has their priorities all screwed up.

    An error occurred while saving the comment
    Futski commented  · 

    @NegaEric - Well said.

    Dr. MS, How about giving us a pain remedy.

    An error occurred while saving the comment
    Futski commented  · 

    @Thomas, I forgot to mention that with a laptop, you need to put it upside-down and stand on your head while working. That's what MS would want you to do. :D
    All joking aside, yea I can see where there is a problem with my suggestion when you don't have a mouse.

    An error occurred while saving the comment
    Futski commented  · 

    @NegaEric. Basketball??? ROLF...…. You just made my day.

    An error occurred while saving the comment
    Futski commented  · 

    There is a less-than-ideal form of smooth scroll already built into Excel. Just click the Mouse Wheel button. You should see a 4-direction pointer appearing on the screen. Then moving the mouse will smooth scroll up, down, left and right. Unfortunately this is a poor implementation of smooth scrolling.

    IMHO, Smooth scrolling should work like this:
    1) If moving cursor by arrow keys and not editing a cell, scroll by cells.
    2) If moving cursor by arrow keys and you are editing a cell, smooth scroll if needed.
    3) If scrolling by mouse wheel, give option for one of 3 scroll options. Note, this option should have it's own icon so it can be added to the menu bars and changed on a whim. Don't hide it in the Excel Options section.
    Scroll Option 1 - Always cell scroll (just like today)
    Scroll Option 2 - Always smooth scroll
    Scroll Option 3 - Hybrid - Cell scroll unless scrolling thru a large cells that wrap off the screen, Then smooth scroll till the large cells are no longer visible, then revert back to cell scrolling.

    An error occurred while saving the comment
    Futski commented  · 

    @NegaEric, Thanks. Still on for the Packers v Seahawks game in 2023? :D

    An error occurred while saving the comment
    Futski commented  · 

    @Brent,
    My apologies to you for accusing you of being all the other artists too.

    @All
    As an explanation for my position; I work for a business that constantly promotes careful communication. As part of that, we are taught to be aware of how others might perceive messages, emails, documents and the like. Doodles would certainly be included as a form of communication. Perception is everything. And while most people would not have any issues with the doodles, some might. Personally, I liked the doodles, but none the less, that is what our company teaches us to avoid.

    I find it very disappointing that I come under personal attack from multiple people for simply pointing out that the doodles could offend some people. Very disappointing indeed.

    To that point, this will be my last post in reference to the doodles or any future personal attacks on me. I am just saddened that we can't keep this thread professional and constructive. C’est la vie.

    An error occurred while saving the comment
    Futski commented  · 

    @Brent / Bill Gates / Patrick / Sundar (probably all the same person)
    You may have intended satirical lighthearted comic relief from the daily stresses of our lives. But you also need to consider the hypersensitive society that we live in. In today’s world you can't just go expressing death wishes on people without the possibility that someone somewhere might just take you seriously. Now that person is not me. I understand your intent, and I know the doodles are just a form of stress relief. But I am saying that other people out there might not understand it the same way. We need to be a careful of what we say and how we say it.

    And [Deleted User] is right, If we continue to just "Bash M$", they'll never pay attention to this suggestion. Maybe I'm being a "Debbie Downer" but lets try to get this back on topic. And lets stop bashing each other, that's not productive.

    Oh yea, thanks for immortalizing me in your comics. I can't wait for the book. :D

    An error occurred while saving the comment
    Futski commented  · 

    Guys,
    Drawings of people killing Eric, or anyone - Not appropriate. If you're gonna do graphics, don't be so violent.

    Just sayin!

    An error occurred while saving the comment
    Futski commented  · 

    @NegaEric

    Want to catch a Packers vs Seahawks game? Oh yea, they don't play this year, bummer. But I'm sure they'll play each other before we get better scrolling. And Seattle's going down....

    Just thought I'd start building our community. LOL

    An error occurred while saving the comment
    Futski commented  · 

    It's pretty clear that MS has given up on reading the entire Excel UserVoice forum. I follow numerous highly voted topics and every one of them say the same thing; that MS isn't listening to the UserVoice. I'm sure everyone here can agree with that.

    On the bright side, it gives us a place to vent... :)

    An error occurred while saving the comment
    Futski commented  · 

    @Roy, They manage to get IE and Word and numerous other software to do a reasonably smooth scroll. Why not Excel. Laziness I presume. Or perhaps ignorance and selective blindness toward of how people actually use Excel.

    Futski supported this idea  · 
  2. 937 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Thanks for supporting this feature. We won’t be able to in the near future, but we understand that it would be a nice improvement. Even though it seems like a straightforward idea, it is quite complex since named ranges can be dynamic, meaning that the range is calculated when the workbook is calculated.

    We’ll continue tracking votes for this suggestion.

    An error occurred while saving the comment
    Futski commented  · 

    @Steven Soeder - I think the problem is, as I've seen stated many times before, that MS doesn't actually have anybody that "uses" Excel. And certainly not anyone that could be considered a "power user" like the majority of people in this forum.

    An error occurred while saving the comment
    Futski commented  · 

    I guess this just proves how un-maintainable this 30+ year old app has become.
    It's too difficult to add named ranges to conditional formatting. But wait, they can add all sorts of new features like the Dynamic Array Functions (#Spill function etc).

    Bottom line is there's no money in it when the fix a broke conditional formatting, but adding new features might attract new customers. Follow the money....

    MS needs to focus on making the existing customers happy, not trying to capture new ones from an already saturated market.

    It's time for a complete rewrite of excel. But that's not likely to happen, at least not before I die of old age.... :-(

    An error occurred while saving the comment
    Futski commented  · 

    @David Ackroyd, I like your solution for cells that are copied outside the defined range. An error message would be perfectly appropriate as the rule would apply to a named range, not a specific cell. I'd opt for a warning with a "Don't show me this message again" option.

    An error occurred while saving the comment
    Futski commented  · 

    @Jan, you are right, there is a lot of shouting at deaf ears. Unfortunately the selectively deaf ears don't want to hear what we're saying. And it's not just this topic.

    Is anyone aware of any recent MS response to any topic??? My guess is that MS has completely abandoned this forum. But they leave this out here to make us feel like they are listening. So sad that a perfectly good tool is going to waste.

    An error occurred while saving the comment
    Futski commented  · 

    I'm not trying to make excuses for MS here, but maybe they don't know how we want excel to work.

    For example, when we copy a cell that is formatted using named ranges to another cell in a different column, in the same table, how should the formatting be copied? Should it make a new rule? Or should it abandon the source formatting and assume the formatting of the new destinations column. I'm for the later.

    What about if you have a format spanning 2 or more columns and I want to insert a column in the middle, should it be excluded from the format, or should it assume the formatting of the columns it was inserted between. And what about moving a column with unique formatting between the two spanned columns? Once again, how should that be handled?

    Let's give MS some ideas how to fix this existing disaster instead of just complaining about their lack of action.

    An error occurred while saving the comment
    Futski commented  · 

    @Sbasu
    I agree with you 100%. I think the difference with my previuos note and what you are describing is that I was applying the conditional formatting to columns in Formatted Tables; ie "Applies To:=Table1[Column1]". I'd guess that you weren't using Formatted Tables.
    To me, a Formatted Table is any table where "Format as Table" was applied.

    For a formatted table, the normal way of adding a new row by simply starting to type in a new row at the end of the table. All call formats and formulas will automatically be applied to the new row. Conditional Formatting will also get applied to the newly added row. Looking at the Cond Format rules will show that the "Applies to" range will be extended to include the new row.
    But as you said, "copying" a cell to a new row will still make a mess. But when it did, the new rule it added was unnecessary.

    Example:
    Table1 = is C2:D11
    Headers for Table1 are in Row 1
    Col C ($C$2:$C$11) formatted for cell = 1
    Col D ($D$2:$D$11) formatted for cell = 2
    Copying C5 to C12 creates a new new row in the table. So the Cond Format for Col C (and Col D) changed to to $C$2:$C$12 (and $D$2:$D$12) in order to accomodate the new table row. But it also added a separate rule just for $C$12. The rule for $C$12 is not needed because the table range was extended. This left 3 format rules; 1) $C$21 2)$C$2:$C$12 3) $D$2:$D$12 . #1 is not needed because it overlaps with #2

    I hope this makes sense.

    I think whats happening is that because you're doing a copy / paste (not paste special values), it insists on copying the Cond Format too even though the format is exactly the same as table column format.

    Bottom line is that this still makes a mess. MS needs to allow us to put "Applies To:=Table1[Column1]" w/o out converting it to a fixed range. And if the Cond Format matches the table columns format, then drop the Cond Format.

    By the way, I do agree with you about paste-special-values. Thats just about the only way I ever paste data. It keeps the formatting rules neat. Unfortunately, a lot of the sheets I create get shared with others that don't understand the intricacies of conditional formats and how copy / paste can mess them up.
    And I too am on O365 V 1804 Monthly Channel

    An error occurred while saving the comment
    Futski commented  · 

    @Sbasu, you are correct. MS does seem to have fixed some of it. It appears to be adjusting the "Applies To: range when you add / delete / move whole rows and columns. Or even if you copy/paste within a single "Applies To: range.

    But alas, the problem still exists when you copy/paste data that crosses more than one "Applies To" range.

    For example:
    Create a table with a conditional format in Column A and different conditional format in column B. If you copy a single cell from a row in column A and paste into a different row but also in column A, it will work as desired without breaking up your rules.

    However, if you copy row data from columns A:B and paste that in a different row, then your rules will get broken, even though the data always stays in the same columns. Same thing would happen if column B did not have any conditional formatting.

    You could MOVE the whole row (shift drag row) without breaking the rule. But sometimes you only want to copy a few cells from a row, not move the whole row.

    So in summary, your rules will get broken/split-up when you copy/paste and the data you are copying spans more than one conditional rule or non-conditional formatted range.

    Clear as mud, right?

    PS, I haven't tried the =OFFSET trick from @JOUKE

    Futski supported this idea  · 
    An error occurred while saving the comment
    Futski commented  · 

    This is a major pain in the back end. Come on MS, it's time to get this fixed.

  3. 1,171 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Thank you for taking the time to share your request for linking min/max values of a chart axis to the cell value! We think this suggestion has merit; however, we don’t expect to devote time to it in the near future. We will continue tracking votes and comments here, and will keep this suggestion under consideration for future development.

    Thank you again, and please keep sharing your thoughts!
    Auston [MSFT]

    An error occurred while saving the comment
    Futski commented  · 

    @Francisco - If you are meaning that you want to change the chart title, axis label, or even the data labels by simply changing a cell value, then you can already do that by replacing the label text with a cell reference ie. instead of "Total Sales", use "=A1". One caveat, you can not use a formula like =A1&" Totals". It needs to be a single cell reference. But A1 could be any formula you want. Then just reference A1 in your chart.

    I use this technique for dynamic charts where both the data ranges and the labels can be changed by simply selecting a the desired options from a few cells that have predefined data validation values.

    Futski supported this idea  · 
  4. 728 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    This is a great suggestion, and we want to keep the interest going. Thanks to everyone who has already voted and commented on the suggestion to have an option for the default paste behavior in Excel.

    Sorry that we’ve been slow to comment and update the status on this one.

    Steve K [Excel]

    An error occurred while saving the comment
    Futski commented  · 

    Tim, I also use O365.
    You may want to check the setting that Roy found.
    File|Options|Advanced|Cut, copy, and paste | Show Paste Options button when content is pasted should be checked.

    An error occurred while saving the comment
    Futski commented  · 

    Roy, Glad it worked for you. And good find on the Options / Advanced / Cut Copy Paste / Show Paste Options. Mine is indeed checked.

    And you are absolutely correct when you you say some options should be carried thru at the spreadsheet level. Default PSV being one of them.

    And like you, Alt-ESV just flows out my fingertips every time I copy/paste. But I / we shouldn't need to resort to that. MS really needs fix this and add a worksheet level default. That way we won't need to go back and fix everybody elses carelessness (I had another word there, but thought it'd get censored :-) .

    An error occurred while saving the comment
    Futski commented  · 

    Roy, Not a cup of water. :-D

    It's not Ctrl-V, Ctrl-V. It's 3 distinct keystrokes
    Ctrl-V
    Ctrl
    V

    You'll see that after the initial Ctrl-V paste, pressing Ctrl all by itself pops up a paste dialog box. Then V for Values only.
    You can also use other options instead of V, like F (Formulas) or B (All formatting except Borders) etc.

    An error occurred while saving the comment
    Futski commented  · 

    Anonymous, That's very interesting. I learned something new today. It's interesting how the initial Ctrl+V pastes with all the formatting but then the subsequent Ctrl, V strips all the pasted formatting thus restoring the cells original formatting, including Conditional formatting.
    I've always used Alt+E, S, V to get the same result. But Ctrl+V, Ctrl, V does the same in a little easier to remember method.
    Thanks for the tip

    An error occurred while saving the comment
    Futski commented  · 

    @Esteban, I agree with you 100%. Pasting a table from a web page should default to values only because the the mess it makes trying to include the formatting.

    An error occurred while saving the comment
    Futski commented  · 

    In todays world of "shared" spreadsheets, I think the setting for default paste type needs to be set not only at the user level, but also at the spreadsheet level. I have seen countless spreadsheets messed up by careless copy/pasting of data.
    Having this option available is of no use on a shared spreadsheet if 90% of the users never change the option from the default of including formats. Therefore, if the option were available at the spreadsheet level, the author could change the setting to over-ride the users default, thus preserving a carefully formatted spreadsheet.

    Futski supported this idea  · 
  5. 1,868 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    Futski commented  · 

    @Zak, My response was not intended to be hostile. I'm apologize if it's worded poorly. I was merely agreeing with you that PHP / SQL is one possible solution.

    As a person who does work in a large corporate IT environment, I can say that we never have IT staff readily available for a small little projects like this. What we do have is an IT staff that is way over worked. We simply would not have the time to code a web page just to import some data unless the user was able to financially justify the cost of the project by proving large volumes of data. And then it ends up in queue for prioritization. And finally some day it may get completed if it provides enough value. That's just the way large corporations work. And that is why the general Excel user base needs Excel to work correctly.

    An error occurred while saving the comment
    Futski commented  · 

    All right Zak, You are correct, there are many ways to solve every problem. And PHP/SQL is one of the options.

    To set the record straight, in my nearly 40 year career, I've coded in more languages than I can remember, including PHP. And I've used more varied databases than I can remember including SQL Server and Oracle (yes there is a difference). So I am well familiar with the capabilities of PHP, SQL, HTML and all that varied stuff going all the way back to the late 70's when I got interested in programming.

    But I'd make the argument that unless, you're expecting many, many customers to send many, many files, a hand coded web page might be over-kill. If it's only one or two customers sending a file once a week, a web page might be hard to justify especially since that exposes your database to the web. Security issues and all.

    PHP/SQL is one alternative, and given the right scenario, maybe even the best solution. But in most cases it's probably not practical.

    Roy, I read sarcasm. You had me ROFL.

    An error occurred while saving the comment
    Futski commented  · 

    You're right Orange. Next time I need to read in a dump of 10,000 records that I need sorted, filtered and totaled, I'll call my IT department and ask the to code me a web page with a backend database. I know, with all the bureaucracy and coding time, it might take a month or two to squeeze it in between other more important projects. And when I get my answer, I'll ask them to throw it all away.

    Oh wait. Let me dump it into Excel. Easy Peezy. Done in 2 minutes.

    If all you have is a hammer, then everything looks like a nail...

    An error occurred while saving the comment
    Futski commented  · 

    @Orange, Please don't misunderstand. I wasn't saying there weren't other solutions. But I was saying that in the corporate world, Excel is undoubtedly the dominant "spreadsheet" because of it's feature set and connectivity to other applications. Even though it's the elephant in the room, it's definitely riddled with massive bugs and other GUI issues.

    You are correct, a PHP based web page might be able to do what you're asking it to do, but if you want it to act like a spreadsheet, then you should just use a spreadsheet. Google Sheets is a perfect example of a very good Web Based spreadsheet. And even Excel Online is starting to get there, but they both have a really long way to go to catch up with Desktop Excel in terms of raw functionality, feature set, and connectivity

    Building a Web Based PHP/SQL server app usually creates a very single purpose application that requires special skills that is generally left to IT type people to create. But anybody can create a spreadsheet.

    Yes, the Web if far more prevalent than Excel. I was never comparing Excel to General Web usage. But when it comes to spreadsheets, in the corporate world, Excel is undoubtedly the dominant spreadsheet and tool of choice for sharing data between people and corporations, as well as number crunching for the average non-technical user.

    Side Notes:
    Excel pre-dates not only PHP and SQL server, but it also pre-dates public use of WWW as well by 6 years. Excel was released in 1985, SQL Server in 1989, WWW public use starting in 1991, and finally PHP in 1994. Dare I say, it probably pre-dates you as well (smile, that's a joke :-) ).

    An error occurred while saving the comment
    Futski commented  · 

    @Karen Grube, At risk of repeating comments from much further below in this thread and for preaching to the choir, I'd like to suggest the following.
    I'm assuming you're getting a CSV file which, when you open it in Excel, automatically reformats you're data into Sci Notation (sigh). Have you tried changing the extension on the file from CSV to TXT and then try opening it. Because it's a TXT file, Excel will force the import wizard to open. Then just specify comma delimited and also change the problematic columns to be 'Text' format instead of the default 'General' format. Hopefully this solves the issue for you.

    While that may solve you're particular problem, it doesn't really solve the bigger issue of this topic. MS still needs to address the issue from a programmatic point of view because it shouldn't be assuming that all large numbers want to be viewed and saved as Sci Not.

    An error occurred while saving the comment
    Futski commented  · 

    @Jason Ericsson, While I do understand that there are many great alternatives to Excel, they are not always an option because of things like
    1) Integration with other tools such as SQL Server
    2) Already coded VBA macros, many of which could not possibly be replicated using tools in other software
    3) Corporate software standards and licensing
    4) Near universal acceptance of Excel as a business tool for sharing data not only within a business but also with 3rd party vendors, customers, and consultants.

    If the data in the sheet is relatively simple and straight forward, then other tools like Google Sheets would work well. But for many of the much more complex scenarios, sadly, there just isn't any other workable alternative. So we're forced into living with all of the all-too-numerous failings of Excel. :-(

    An error occurred while saving the comment
    Futski commented  · 

    @Edward Bemis - change the file extension from .CSV to .TXT. Then when you open the file, Excel will be forced into use the Import Wizard. From there specify comma delimited. And then for the UPC column, specify Format as Text.

    It's a $#!++^ workaround, but it works.

    An error occurred while saving the comment
    Futski commented  · 

    I don't believe this in really a bug, but rather it's operating as designed. My guess is that it's history goes all the way back to the "Start" of Excel, at a time when memory was at a premium, so the most efficient way to store the data was in Sci Not.

    But in todays day and age when memory is no longer an issue, there is no reason why MS can't address this issue to make it much more useable for the masses. It should be an option for those that need it, but it should not be the default for the majority of Excel users.

    An error occurred while saving the comment
    Futski commented  · 

    @Roy, You're right on the mark... Double thumbs up to ya.

    An error occurred while saving the comment
    Futski commented  · 

    One of the main problems with the importing CSV files is that Excel does not follow all the rules of a proper CSV file import. CSV's are supposed to always treat quoted text as text. But even if you have a number in quotes, Excel will still treat it as a number, not text as desired. So as @Corin Dennison said, "01200E05827005" would still get imported as a "Scientific Notation" number.

    In addition, a Text formatted column should always export to a CSV with Quotes, but Excel doesn't unless there are special characters embedded that require quotes, like a space character.

    Opening CSV files never open the Text Import wizard because the file extension implies that it's columnar data. .TXT files, however can open with the Import Wizard depending on how you open it.

    Bottom line is that the only way to have a long number imported w/o potentially translating it to Sci. Notat. is to have the data in a TXT file and use the File Import wizard to convert the number column to text.

    This is less than ideal for sure. An option to not convert to Sci Notat would certainly help especially if other data in the column is not in Sci. Notat.

    An error occurred while saving the comment
    Futski commented  · 

    The real problem is not limited to importing text data. Lets say you're entering a 15 digit (all numeric) part numbers into a cell. Excel will automatically reformat you're part number into scientific notation. Why? It needs to stay as 15 digits. And sometimes, you might even want leading zeros retained.

    An error occurred while saving the comment
    Futski commented  · 

    @Anonymous, Let's see, what can we expect from a Monopoly.

    Community Chest
    Go to Jail
    Go Directly to Jail
    Do not pass Go
    Do not collect $200

    Sounds about right huh?

    An error occurred while saving the comment
    Futski commented  · 

    @Roy,
    Why does that not surprise me!!! If MS wants to support CSV, they really ought to do it right. Thanks for trying.

    Hey MS,
    Double Quotes in - Format as Text
    Formatted as Text - Double Quotes out
    Should be simple. Lets get it done.

    An error occurred while saving the comment
    Futski commented  · 

    If only Excel would save Text Formatted fields with double quotes around them in the CSV file (a csv standard), then the problem would be solved.
    If only... sigh...

    Futski supported this idea  · 
  6. 1,276 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Thanks for the support and the detailed discussion around this suggestion. We understand that there are some advantages and disadvantages with both MDI (multi-document interface) and SDI (single-document interface), and we currently do not have plans to revert to MDI. We do want to improve the experience with SDI so you can get your work done efficiently, and this post has helped toward that goal.

    Some of the specific issues mentioned are addressed as follows:
    – Stability: This has been a focus over the past several years, and the monthly releases in 2020 have been among the most reliable ever in terms of avoiding crashes.
    - Screen space – while it won’t get all the space back, you can minimize the ribbon to save some space. It only shows when needed.
    - Navigation between workbooks: you can use CTRL+F6, SHIFT+CTRL+F6, CTRL+TAB or SHIFT+CTRL+TAB to switch to the next workbook. …

    An error occurred while saving the comment
    Futski commented  · 

    @Anonymous, there are plenty of times that I find multiple instances of Excel useful (copy & paste between workbooks on multiple monitors comes to mind). So SDI does have it's place. That said, users should be given a choice. Let the users choose their default SDI or MDI. But then let them rip off a tabbed workbook to a new instance if desired, or combine 2 instances into one.

    An error occurred while saving the comment
    Futski commented  · 

    I didn't mean to hijack this thread to be a VBA discussion, so this will be my last post in this thread about VBA. But I did want to clarify a little.

    VBA is simply the programming environment and it's associated language. VBA is the look and feel of the VBA IDE as well as the core language components of VB (IF-then-else, Do While, Case, etc.).

    But VBA is NOT "Activecell.select" or "Selection.Cut". Those belong to Excel Libraries which are automatically added into your VBA project. This is what allows VBA to talk to Excel.

    MS never said it will discontinue development of these Excel Libraries. In fact these libraries are probably exactly the same libraries that Excel itself uses to do virtually everything. If MS stops developing these libraries, then all changes (good, bad, or indifferent) to Excel would also stop.

    So what I'm trying to say is that the VBA IDE and core VB language may no longer change, but the functionality within a VBA macro will continue to change and grow as Excel (and its libraries) change. This should include new MDI functionality (if we ever get that back) because Excel itself will be using the same libraries as VBA does.

    Roy, I know what you're saying about using VBA to connect to other office apps. It's a major pain in the back end. But I've done it multiple time. I've used Excel VBA to pull data from Access databases based on user entry. I've even done that to MS SQL Server databases. I have also created macros that save the current worksheet (tab) to it's own separate workbook and then attached that workbook to an Outlook email and automatically sent it. All invisible to the user. And I've seen many other examples of people doing similar things.

    So while it might be a PITA to accomplish inter-application functionality, I wouldn't rule that out as something thats never being done.

    There, no move VBA discussion for me, at least not in this thread.

    An error occurred while saving the comment
    Futski commented  · 

    IMHO the real reason MS killed MDI, is for security / stability reasons (actual stability improvement is debatable). Anyway, one bad acting spreadsheet or VBA module gone awry was able to lock up or bring down all spreadsheets running under a single Excel MDI instance. I believe their intent was to prevent one spreadsheet from crashing them all and losing their associated changes. But in todays day, improved containerization of code and data should easily allow MS to fix the original problem, thus allowing them to bring back MDI. This is basically the same way bad acting web pages no longer bring down the whole browser, but rather just the bad page.

    Mats Samuelsson, regarding Visual Studio, it is not a replacement for VBA, nor is VBA a replacement for Visual Studio. They are completely distinct entities with very little overlap except for the "Visual Basic" part of the name. One cannot create a simple VBA macro using Visual Studio, nor can one write code for an Arduino using VBA.
    For those interested in the history, VBA is based on ancient Visual Basic 6. VB6 was discontinued 20 years ago. Visual Studio continued to advance VB.net into a very modern language today, but it's almost completely incompatible with old VB6 code. And with VBA being a derivation of VB6, there is almost no crossover available. Fortunately MS has no intention of dropping VBA because of the countless lines of code written in it.

    An error occurred while saving the comment
    Futski commented  · 

    Richard Laycock and Anonymous, there is no reason to accuse Daniel of not knowing how to use Excel. He has his preference just as you have yours. He simply doesn't want SDI to go away. I'm certain he'd be OK with being given a choice between SDI and MDI, just as you are.

    An error occurred while saving the comment
    Futski commented  · 

    Thanks Roy. I'm still stuck back at Version 1902 (Build 11328.20158). I'll need to wait for corporate to push the change to my PC. So it must be new functionality in 1903.

    An error occurred while saving the comment
    Futski commented  · 

    Roy, Thanks for the info. What Version / Build do you have. I don't seem to have this change yet. Thanks.

    Futski supported this idea  · 
  7. 173 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    Futski commented  · 

    @Nik W - You are 100% correct. As a fellow coder, I can attest that changing the window to resizable is mere child's play. Very sad indeed especially given the frustration of having to deal with fixed width windows. Real PITA when dealing with long rules etc.

    An error occurred while saving the comment
    Futski commented  · 

    "Not at this Time" says admin. How disappointing. This could have been a very simple change. It's not like a re-sizable form is a big deal.
    MS should be assigned to a rookie coder. What a great way for them to get their feet wet after joining the Excel Dev team. Just change the pop-up form type from Fixed to Re-sizable and add a little code to adjust the text boxes inside the form. I've done this myself in many VB apps. Child's play.

    An error occurred while saving the comment
    Futski commented  · 

    Personally, I think ALL popup windows should be resizable. There is no reason anymore that, other than laziness, that MS should have any fixed size pop-up windows. I'd be happy even if it didn't remember the last size the window was. But for the love of Pete, make the windows resizable, especially if they contain formula text boxes. This should be an easy one to fix.

    Futski supported this idea  · 
  8. 1,489 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Thanks very much for your votes. And to those who took the time to fill in the survey, thank you! This is a brief update to let y’all know that we’ve started work on this feature request along with the one on changing numbers to scientific notation.

    - Urmi [Msft]

    An error occurred while saving the comment
    Futski commented  · 

    MS needs to correct Excel such that it follows normal convention for importing and exporting CSV data.
    When importing a quoted CSV field, either text or a number w/leading zeroes, then those quoted fields should be formatted as "Text" in Excel. That way you can import numbers containing leading zeros w/o losing the leading zeroes. Conversely, all text formatted cells should be saved as Quoted text in the CSV regardless of if it looks like a number or not.
    An extension to this would be a column that has a number format which adds leading zeros could also be saved in the CSV as quoted text with the leading zeros.
    This would also solve the problem of importing/exporting cells that look like they could be in Sci Notation; if it's in quotes, then it's text, period bottom line, and it shouldn't be treated as a number, not now, not ever.

    Futski supported this idea  · 
    An error occurred while saving the comment
    Futski commented  · 

    Importing CSV's has always been a very weak point for Excel. It never get's it right. But I do understand why excel strips the leading zeros, because that's the normal convention for displaying numbers. But I too have been burned by Excel ALWAYS converting the data to numbers (if it looks like a number). A good start would be if Excel simply honored a Double-Quote as text and always text, even if the data looked like a number.

    I've also been burned by Excel converting my data to Scientific notation. ie. importing "20E3" converts to Scientific Notation ==> 2.00E+03 . Come on MS, what's the deal with that. Do you really think I intended it to be Scientic Notation. Expecially if it's in a column with other text data like "20K3".

    Best solution would be to ALWAYS popup an import dialog (when opening a CSV) and allow us to select the column format we want. And being that it starts as a CSV, break it down to it's constituent columns for us, not the normal column based import dialog. And while you're at it, let us apply/create a number display format for a column while we're importing it.
    I'd also recommend the same dialog for exporting CSV's, so we can specify Double Quotes on a number column if desired.

  9. 128 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Futski supported this idea  · 
  10. 37 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    Futski commented  · 

    Unfortunately MS is no longer actively developing VBA. It is as far along as it will ever get. The Excel libraries will probably be updated as new features are added to Excel, but I don't expect to see any further enhancements to the VBA IDE itself. Fortunately, MS has no plans to discontinue VBA either. There are too many millions of lines of customer VBA code written for MS to just kill it. Killing VBA would probably be the death of Excel. Here's a short little writeup written by a MS Excel MVP that explains the future of VBA.
    https://www.quora.com/Since-VBA-is-no-longer-supported-is-it-going-to-be-replaced-in-Excel-by-some-other-language

    On a positive note, I have also read that MS is planning on replacing VBA with something a little more robust. Perhaps, and this is just a wish list item for me, MS will integrate VBA like development into Visual Studio, which is capable of supporting many different languages, including 3rd party languages. Just imagine the possibilities if you could pick the language you wanted to write your macro in.

    I'm keeping my fingers crossed for a more robust environment than VBA provides.

  11. 5 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Futski supported this idea  · 
  12. 3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Futski supported this idea  · 
  13. 3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Futski supported this idea  · 
  14. 3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Futski supported this idea  · 
  15. 7 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Futski supported this idea  · 
  16. 5 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Futski supported this idea  · 
  17. 10 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    Futski commented  · 

    Under the Date Category (in number formatting) , there is already a mm/dd/yyyy hh:mm PM format which might work for you instead of creating a custom format. Same in the Time category.

  18. 848 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Futski supported this idea  · 
    An error occurred while saving the comment
    Futski commented  · 

    Ditto on Lubomír Tosek's comment. Lets see Left Across Selection and Right Across Selection too. And add vertical across selections too.

  19. 48 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Futski supported this idea  · 
  20. 65 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Futski supported this idea  · 
← Previous 1

Feedback and Knowledge Base