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

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

Another attempt at building a csv line parser for Alpha5

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

    Another attempt at building a csv line parser for Alpha5

    If you need more programmatic control over the importation of CSV files than the Alpha5 standard functions provide, here's my latest attempt: CsvLineParse2(), a user UDF for use with Xbasic.

    Input to this function is a line of csv field names or field data to parse. Output are the field names or data as a CRLF separated list, which is a format easily handled in Alpha5 Xbasic.

    Example:

    �"She sells, sea shells", "on the sea, shore",12345�

    Becomes:

    �She sells, sea shells
    on the sea, shore
    12345�

    The csv conversion is done according to the RFC 4180 standard. More information here.

    Particulary, the parsing must take account of commas within quoted fields and quotes within quoted fields. In the latter case quotes are escaped with a second quote, as in "". Example: �"""Hello"", she said."� is parsed as: �"Hello", she said.�

    Commas can be field separators, so the code has to differentiate between comma field separators and commas that are not field separators. Also between quotes that are field delimiters and quotes that are just part of the field contents.

    Not particularly efficient at 1.3 seconds per thousand records processed (on my PC with a Windows Experience Index of 5.6), this code does however work. I am not however yet claiming it is entirely bug free!

    Preferably I would like to see the processing speed under 0.5 seconds per thousand records processed. But that will have to be for another day.

    I have tested and so far been unable to find on the Internet any other code, including regular expressions, that is both suitable for use with Alpha5 and that meets the RFC 4180 standard. But I am still looking.

    Attached is a zip file containing the Xbasic function CsvLineParse2(), a test Xbasic script and a test file of CSV data.

    Any suggestions or improvements, just let me know.
    Attached Files

    #2
    Re: Another attempt at building a csv line parser for Alpha5

    Hi Brett,

    I have not looked at you sample yet but have a look at this function and see what it does to the speed of your Parse.

    tbl.batch_begin()

    your process

    tbl.batch_end()

    Let me know how this works for you.
    Regards
    Keith Hubert
    Alpha Guild Member
    London.
    KHDB Management Systems
    Skype = keith.hubert


    For your day-to-day Needs, you Need an Alpha Database!

    Comment


      #3
      Re: Another attempt at building a csv line parser for Alpha5

      Hi Keith. Yes, good suggestion. I use batch_begin and end a lot. They make big improvements in the speed of processing of tables when both reading and updating a table at the same time. Unfortunately here though I am reading and not updating a csv text file and not a table. So there is no corresponding improvement in throughput to be expected. I tend to use <file>.read_line(). There is probably a much more efficient way to process a text file but I haven't stumbled across it yet.

      Comment

      Working...
      X