The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic

Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.

If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.

Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.

Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Export to excel adding extra columns

  • Filter
  • Time
  • Show
Clear All
new posts

  • Export to excel adding extra columns

    Hello again,

    I'm following Selwyn's video for advanced Excel export. I create a simple test report, convert it to layout and then from the grid I have a button that uses the advanced Excel export. When the spreadsheet opens there is a blank column between every cell.

    Here is how it looks in design view:


    Here it is if I print it to the screen:


    and here it is when exported to Excel


    Does anybody know why there are blank columns? It happens even if I try to export to Excel from the preview screen.



  • #2
    Re: Export to excel adding extra columns

    Just used an existing list, an existing report and added a button to export to excel and it worked with no blank columns.

    The thing that stops me using this feature is the apparent lack of conditional formatting and word wrapping of cells available.

    With fear of getting this post wiped, just tried the same in Filemaker and got a similar result to Alpha, although I did not have to add the buttons for excel or pdf they were already there in preview mode.


    • #3
      Re: Export to excel adding extra columns

      It appears that it is adding columns if you start the report initially as a freeform report, save it, then convert it to a layout. On both my home PC and my work PC it adds the blank columns. If I create the report directly as a layout report then it works. Would somebody be kind enough to just double-check that for me on your PC.

      I just had a simple test table with some random numbers, IE:

      ID, Males, Females

      Created a Freeform report (in projects) [ID][MALES][FEMALES] (no spaces) and then converted it to Layout. From a button on a grid I used Advanced Export, nothing fancy, and I always get blank columns.

      Then I created a Layout report {ID}{MALES}{FEMALES} and From a button on a grid I used Advanced Export, nothing fancy, and it shows in Excel with no blank columns.




      • #4
        Re: Export to excel adding extra columns

        Hi John,

        I tested this and do get the same as you are seeing, but I believe it is part of the conversion from a freeform report to a layout table report.

        It seems no matter how close together your fields are in your freeform report (even overlapping which throws up a warning) once it is converted to a layout table report there is a column inserted between them in the layout. You can select and delete these columns in your layout, but be careful because some cells can be merged to make the layout table look as close to the freeform layout as possible, best to have visible gaps between your fields in your original freeform report, and then when exporting to excel you do not get the rogue columns appearing.


        • #5
          Re: Export to excel adding extra columns

          Hi Lance,

          Thanks again. At least I now know I'm not imagining it. Funny enough, I didn't even notice those rogue columns, now you pointed them out, it seems so obvious.