Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook



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

Preparing a spreadsheet to be imported

  • Filter
  • Time
  • Show
Clear All
new posts

  • Preparing a spreadsheet to be imported

    When I began experminenting with the ole automation samples provided with A5V5 I lamented that the "read from" capability available in V6 (see the section in the .chm "Reading an Excel Spreadsheet with OLE")
    was not available to me. I wanted to read through an excel spreadsheet, excerpting certain portions and saving the result as an Alpha import compatible excel version. I found the limitations of ole in V5 can be circumvented.

    The attached script processes a spreadsheet report that is available in my company. The original of the report contains data pertaining to three sales divisions. I was asked to take the data for one division and make it available in my in-house application. This is easily accomplished if I manually strip out the data I want, title the columns as needed to fit a predefined import operation, then save the file as Excel ver 3/4, then run the import. The problem with that scenario is that I must perform all these steps once a week. I was determined to automate the whole process.

    Using the code snippets others have posted on the board attributed to John Magno -, I came up with the attached script. It is not a finished product that you can use in your own work "as is" but it should provide a basis for creating your own process. It is fairly well commented so I will finish by pointing out that the script....

    opens an excel file of an version suported by your excel application
    reads the excel file looking for predefined values in certain cells
    deletes the sections of the file that I don't need
    renames the columns with usable values
    saves the file as excel v 4, ready for import

    There can be only one.

  • #2
    RE: Preparing a spreadsheet to be imported

    I may use that one in the near future.

    Thanks Stan.
    AlphaBase Solutions, LLC


    • #3
      Hi, I'm interested in reading that code, but it won't download ... says not available, is it still in the code library? thanks.


      • #4
        Me Too please


        • #5
          Here's something similar

          Originally posted by Lance Gurd
          Me Too please
          I can't locate the original at the moment. This doesn't rename the columns but has the rest, I think.

          FUNCTION ex_convert AS C (excelname AS C, newname AS C ) 
          Dim xlApp as p 
          dim myCell as c
          xlApp = ole.create("Excel.Application") 
          'xlApp.Visible = .T. 'comment this line out if you don't want to see Excel
          xlApp.Selection.Delete(-4162) '-4162 is shift remaining cells up
          xlApp.Selection.Delete(-4159) '-4159 is shift remaining cells left
          xlapp.DisplayAlerts = .F.
          xlApp.ActiveWorkbook.SaveAs(newname,33) '33 is a constant for Excel 4.0, dbf4 is 11
          xlapp.DisplayAlerts = .T.
          END FUNCTION 
          'to call the function, use the example on the next line 
          Found the original attachment!
          Last edited by Stan Mathews; 03-28-2006, 03:24 PM.
          There can be only one.


          • #6
            Updated for post A5V5

            Later versions of Alpha are more strict about using excel methods as

            .select() rather than .select .

            This attachment is updated to reflect that requirement.
            Last edited by Stan Mathews; 03-28-2006, 03:24 PM.
            There can be only one.