Announcement

Collapse

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

XLSX header change

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • XLSX header change

    I have an app that imports an Excel XLSX file, updates a quantity, adds a few new records and then exports the result back out as an XLSX file.

    My problem concerns the header in the file (column names)

    When I import the XLSX file into A5, any column titles with a space are converted into field names with an underscore instead of the space.
    Example: Product ID becomes Product_ID

    For the export file, I need to have the original column titles rather than the field names that A5 converted them to. The resulting file is imported into my customers cash register system.

    Short of having my customers manually change them from and underscore to a space, is there a way to have A5 do it?

    Thanks.

  • #2
    Re: XLSX header change

    Until I can figure this out, my stopgap solution is a dialog telling the customer to change the underscores to spaces.
    Not very elegant but it'll have to do for now.

    Comment


    • #3
      Re: XLSX header change

      You can use the Alpha OLE methods to open the exported file and rename the column headers.
      There can be only one.

      Comment


      • #4
        Did you ever figure out a solution for this? I am having the same issue. I need column headers with blank spaces, not underscores.
        Richard Urban

        Grocery Delivery Software for Stores and Entrepreneurs: http://www.urbangrocery.com

        Comment


        • #5
          I don't know if he did, but here's a link for an example of opening a spreadsheet and manipluating it after the fact:
          https://documentation.alphasoftware....preadsheet.xml

          It uses the Office::ExcelDocument and Office::Spreadsheet objects to manipulate the spreadsheet after you saved it. It's pretty simple to do. I haven't done it in Alpha, but have used this methodology in many other languages. Was glad to see that they had this functionality.

          Comment


          • #6
            Does the export file have to be XLSX? Can it not be CSV. With the data saved as CSV, it is simple to change the title formats. Can you introduce a temporary exchange table?
            Mike W
            __________________________
            "I rebel in at least small things to express to the world that I have not completely surrendered"

            Comment


            • #7
              The documentation may be confusing to some, so here's a simpler adaptation...

              This is a very static solution. To make it more dynamic, you can use STRTRAN() between the read and write lines to use the existing headings replacing the underlines ( _ ) with a blank space.

              Code:
              '  CHANGE THIS LINE TO SET THE NAME OF THE SPREADSHEET WITH COLUMNS TO BE CHANGED
              
              vcExcel_File = "c:\YOUR_EXCEL_SS_NAME.xlsx"
              
              '  CHANGE THIS LINE TO SET THE WORKSHEET NAME YOU WANT TO ADDRESS WITHIN THE SPREADSHEET(Sheet1, Sheet2, etc)
              
              vcSht_Name = "Sheet1"
              
              ' THESE 2 LINES DELETES VARIABLES, THEN SETS THEM IN THE 2 LINES THAT FOLLOW
              
              delete Doc
              delete Sheet
              
              dim Doc as Office::ExcelDocument
              dim Sheet as Office::Spreadsheet
              
              '  THIS SECTION LOADS THE XLXS, FINDS THE WORKSHEET, READS WHAT IS IN THE TOP ROW FIRST FIVE CELLS, AND WRITES THE VALUES
              
              if Doc.load(vcExcel_File)
              if Doc.FindSheet(Sheet,vcSht_Name)
              cellA1v = Sheet.Read(1,1) Sheet.Write(1,1,"Ship To") cellB1v = Sheet.Read(1,2) Sheet.Write(1,2,"Invoice Date") cellC1v = Sheet.Read(1,3) Sheet.Write(1,3,"Item Description") cellD1v = Sheet.Read(1,4) Sheet.Write(1,4,"Price") cellE1v = Sheet.Read(1,5) Sheet.Write(1,5,"Invoice") Doc.save(vcExcel_File)
              end if
              ' THIS NEXT LINE, IF UN-REMMED, SHOWS THE VALUES IN THE CELLS YOU REPLACED ' ui_msg_box("Previous Cell Headings",cellA1v + crlf() + cellB1v + crlf() + cellC1v + crlf() + cellD1v)
              end if

              Comment


              • #8
                The built in Excel coding doesn't allow for that, but you can call the COM object and have total control. This requires Excel to be installed on the server whereas the built in does not.

                To create an object to Excel, you can use the following commands
                Code:
                dim Excel as P
                Excel = ole.getobject("", "Excel.Application")
                dim Sheet as P
                Sheet = Excel.ActiveSheet
                '
                '
                'Close Excel
                Excel.Quit()
                delete Sheet
                delete Excel
                To open an existing file, use
                Excel.Workbooks.Open("filepathandname")

                To Save, use
                Excel.ActiveWorkBook.SaveAS('filepathandname', filetype)

                The SaveAs takes 2 parameters, one of which is the type (CSV is included in these. It is a number. I don't have it readily available, but you can lookup any of these online easily.

                All of the methods and properties are easily available online with plenty of examples. So, this provides complete control over the Excel file including the type of file.

                Downside is that it requires Office to be installed on the server. Upside is that you have total control over all aspects of Excel.
                Last edited by ddprlewis; 06-12-2020, 11:49 AM.

                Comment


                • #9
                  whenever i have to do something like this, i typically save the export to a temporary excel file.
                  then i create a master excel workbook with the code i need to run and manipulate any data in the temporary file, format it, create a table, or whatever. sometimes i put the code in a workbooks_open module so it runs as soon as the file is open. sometimes i use a button and have the use click the button in the "master" to open the temporary file, manipulate the data and then save it as a new name, copy it to 3rd workbook, and then close the master and delete the temporary file.

                  so the alpha code would export and save the temp file and then open the master file that does the work. i started doing this because v11 manipulation of spreadsheets did not work. was fixed in v12, but i have a lot more control of what i can do,

                  a basic example is a query that downloads thousands of rows or rebate data from and ibm iseries into a spreadsheet. then my master spreadsheet opens this workbook, breaks the data out by customer into a new workbo0ok, creates a table, creates a pivot table, formats columns of data, put totals on some columns and emails it to the specific customer. there are hundreds of customers.

                  if you're interested in more specific info for your situation, let me know.

                  Comment

                  Working...
                  X