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

Export takes way too long

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

    #16
    RE: Export takes way too long

    Ray:
    I went ahead and indulged myself in reading the thread. You have to forgive me, but whenever I see threads with responses with half page long xbasic, I feel something ain't right and I move on !! but your thread addresses an interesting issue. I have few observations:
    1-If all you are trying to do is export to a text file, then how about the following suggestions:
    a-Have you tried to use a blob? I am no expert on blobs, but the xbasic most likely would be something like this:
    "TBL".RECORD_DATA_GET()
    FILE.FROM_BLOB()
    In this case there are no filters involved and no querries.
    b-Have you tried to simply save the form layout as txt, or create a report then print it to a text file? Would that be any faster? The xbasic would be:
    query.filter = ""
    query.order = ""
    :Form.SaveAs("form_name","TXT",query.filter,query.order,"",.T.)
    c-How about merging into a text file instead of exporting? how does that compare in terms of speed?

    2-I am not sure I see where does the speed comes from in your work-around: you are still using a query and a filter. In the filter, instead of using between(), you are using query.filter = "recno() = " + record_number which is still a filter. I thought you blamed the delay on filters and you were trying to get away from having to use a filter. One would conclude then that the delay comes from the expression itself (between()) and not simply from using a filter per se.

    3-Your thread opens the door to an important issue: while I am not in the importation/exportation business and I suspect a lot of users are not, but more often than not users need to perform functions on the current record, more like printing the current invoice or the like. The method I use to accomplish that is the one I suggested earlier. I do not have a million-record DB and as such never sensed any delays. But, if there is a better way to export the current record more expediously, then maybe the same concept should be applied to other more commonly used functions on current records. As I said, it might be simply a matter of changing the filter itself.
    Gabe

    Comment


      #17
      RE: Export takes way too long

      Gabe,

      The bottom line is that none of this is any longer pertinent as Selwyn is fixing the problem (see my bottom post on this thread). Now, everyone can stop reading!

      But just a comment or two anyway:

      I did not blame the problem on a filters per se. It was only when one ran the saved export from an action script genie that is supposed to filter for the current record only. Put the same filter in some Xbasic code that the saved export generates and with one somewhat minor exception the problem goes away. That was a pretty clear indication that something was wrong inside the bowels of A5.

      As is almost always the case, there are a number of ways around all the problems. However, none of them (except hopefully Selwyn's fix in the next patch) accomplish what is really needed: a way for novice users to create and modify exports without resorting to Xbasic and all kinds of other sophisticated rigamarole. This is so important to my client, who is deeply into the import/export aspect of A5, that having this fixed in v6 may be enough to move him into v6 (his v5 has the same problem and of course it will never be fixed there). And remember, the time lag would never be bothersome on samll tables.

      As for the length of some parts of the thread: The initial post was not really all that long and the initial question was pretty straightforward. But things did grow once the real issue and possible solutions beacme clearer. Also, what you note about these kinds of posting is interesting and almost universal and applies equally to e-mails. I hate to think about the number of times I have sent an e-mail to a client asking 3 questions in no more than maybe an inch of text, only to get back an answer to only one of them, as if the other two did not even exist. For some reason in these kinds of environments, ... what? I don't really know, but it is an interesting phenomenon.

      Ray

      Comment

      Working...
      X