Feedback by UserVoice

Anonymous

My feedback

  1. 1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Anonymous shared this idea  · 
  2. 7 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Anonymous supported this idea  · 
  3. 9 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
    Anonymous commented  · 

    It should be the same dimensions as if you were to copy the visible cells to the clipboard. When you do a copy on a range in Excel, only the visible cells in the range are copied and the clipboard will basically be a tab separated value string. If that string were parsed into a 2d array, then you'd have an array of the Range.Text property(not Range.Value or Value2). The other way you could do this is to loop over the areas to build the 2d array and this could be done using Value or Value2. Both of these methods are overly complicated and there should be built in support for this.

    Anonymous shared this idea  · 
  4. 94 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
    Anonymous commented  · 

    The reason I suggested new properties is because perhaps UsedRange is being used in current addins and macros where they want the last cell with formatting and not the last cell with data. Changing UsedRange could introduce backwards compatibility issues with some addins. Maybe adding a new property Worksheet.DataRange would be best since it implies only cells with data whereas UsedRange applies to cells with data, formatting, or cells that previously had data(assuming the file hasn't been recently saved)

    Anonymous shared this idea  · 
  5. 7 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Anonymous shared this idea  · 
  6. 43 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Anonymous shared this idea  · 
  7. 20 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Anonymous shared this idea  · 
  8. 36 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Anonymous shared this idea  · 
  9. 210 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
    Anonymous commented  · 

    I highly doubt that Microsoft will ever create 64 bit versions of those ActiveX controls. Read more here https://msdn.microsoft.com/en-us/library/office/ee691831(v=office.14).aspx#odc_office2010_Compatibility32bit64bit_ActiveXControlCOMAddinCompatibility

    If you want to have both 32 bit and 64 bit support for your app consider switching to using .NET for your app development. VBA is a legacy language(it's nearly identical to VB6 which is long obsolete) and should not be used for development of any serious apps. You would do much better using .NET via COM Interop to interact with the Excel object model for Excel Windows Desktop Development. Check out AddInExpress, VSTO, and Excel DNA. I highly recommend AddInExpress, you can create an app that runs on any Excel Version with any architecture (64 or 32 bit) all from a single code base. Excel also has a Java Script api that can do cross platform addins for Excel but it is not as powerful for Windows desktop development.

  10. 14 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Anonymous supported this idea  · 

Feedback and Knowledge Base