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
Devcon 2020 Goes Virtual! LEARN MORE >

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 operation won't export

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Export operation won't export

    I have created an export operation that is exporting records based on a very specific list of criteria. I can get the filter I have written to work within a Browse, but when I copy the same criteria into an Export file it won't run. It does nothing. Any ideas as to why? I have A5v4.03.

    It is a huge (to my sense) filter string. Would that have anything to do with it? Here's the string:

    MARKED()=.F..AND.DELETED()=.F..AND.DOMFOR='F'.AND.(ISBLANK("HERENOW").OR.HERENOW=.F.).AND.ISBLANK("DTNOMAIL").AND.(ISBLANK("MAIL_ADMN").OR. MAIL_ADMN=.T.).AND. (SPKSENGLSH=.T..OR.ISBLANK("SPKSENGLSH")).AND. (IF((VAR->ASKC_SEASON_SUMMER_WINTER)='W',SEASON'S',SEASON'W')).AND.(COUNTRY="AUSTRALIA".OR.COUNTRY="AUSTRIA".OR.COUNTRY="BAHAMAS".OR.COUNTRY="BELGIUM".OR.COUNTRY="BERMUDA".OR.COUNTRY="CANADA".OR.COUNTRY="DENMARK".OR.COUNTRY="FINLAND".OR.COUNTRY="FRANCE".OR.COUNTRY="GERMANY".OR.COUNTRY="CHANNEL ISLANDS".OR.COUNTRY="ENGLAND".OR.*LEADING(COUNTRY,"GB").OR.COUNTRY="ISLE OF MAN".OR.COUNTRY="NORTHERN IRELAND".OR.COUNTRY="SCOTLAND".OR.COUNTRY="GREECE".OR.COUNTRY="GRENADA".OR.COUNTRY="IRELAND".OR.COUNTRY="ISREAL".OR.COUNTRY="ITALY".OR.COUNTRY="JAMAICA".OR.COUNTRY="JAPAN".OR.COUNTRY="NETHERLANDS".OR.COUNTRY="NEW ZEALAND".OR.COUNTRY="PORTUGAL".OR.COUNTRY="SPAIN".OR.COUNTRY="SWEDEN".OR.COUNTRY="SWITZERLAND".OR.COUNTRY="VIRGIN ISLANDS")

    I have a work around by selecting export based on current selection of records, but I would rather not have to have the user run the browse before they export.

    Thanks for whatever support you can give.

    Jason Hunsberger

    P.S. sounds like the conference was great!
    Tags: None
    #2
    RE: Export operation won't export

    I'd be willing to bet you have too many .OR. statements. I've run into that problem when I exceed about 12.

    Now, assuming you have to have all those countries...a couple thoughts:

    Could you specify the filter to exclude a few countries instead of including so many?

    Maybe you could define a country code, such that countries that often go together have the same first character (i.e., UK=101, Germany=102, France=103, etc., then use LEFT(COUNTRY,1)="1").

    If you can't find a good way to group them, you could export records from the first country to a new table, then append that table with the next country, then the next, etc. It's a cumbersome solution, but might be necessary.

    Comment

      #3
      RE: Export operation won't export

      Bill's idea is very sound. You could add a field to your table to hold this country code. One multi digit character field could be used to hold multiple groupings information by parsing the field for various characters in each of the positions, i.e. substr(cntrycode,3,1) = "M" for a group of one or more countries signified with a string like "XXMXXXX".
      There can be only one.

      Comment

        #4
        RE: Export operation won't export

        jason:
        try adding a field to your country table called area.
        group the countries that you want to export into areas.
        then just use one or two areas
        if countryarea = xxx or countryarea = xxx
        Charlie Crimmel

        Comment

          #5
          RE: Export operation won't export

          Jason, another approach to this would be to use two operations. In stage one 'copy' records to a temp table that meet your threshold requirements, but include all countries.

          In stage two open the temp table and 'export' just the country records you want.

          -- tom

          Comment

            #6
            RE: Export operation won't export

            Thank you all for your input. It turns out that the length of the string was the problem. I liked your ideas for creating a country code, but I don't have time to implement all of the changes needed to do that. Instead I created another table with all of the countries and a flag indicating if that country is supposed to be included in the operation.

            For example:
            Argentina .F. '.F. meaning don't include this country
            England .T. '.T. meaning include this country
            Australia .T.
            Scotland .T.


            I then filtered based on the following code:

            MARKED()=.F..AND.DELETED()=.F..AND.
            IF(DOMFOR='F', LOOKUPL("F",COUNTRY,"Mail_Valid","Tbl_Ten_Valid_Country.DBF","Cntry_Trim"), .F.)
            .AND.(ISBLANK("HERENOW").OR.HERENOW=.F.).AND.ISBLANK("DTNOMAIL").AND. (ISBLANK("MAIL_ADMN").OR.MAIL_ADMN=.T.).AND. (SPKSENGLSH=.T..OR.ISBLANK("SPKSENGLSH")).AND. IF((VAR->ASKC_SEASON_SUMMER_WINTER)='W',SEASON'S',SEASON'W')

            The key piece being the statement:

            LOOKUPL("F",COUNTRY,"Mail_Valid","Tbl_Ten_Valid_Country.DBF","Cntry_Trim"), .F.)

            This statement runs a lookup from the main table to the secondary countries table. It works, however what I don't understand is why it works. According to the documentation, in the example of the four countries listed above if the first parameter in the Lookup statement is "F" it should return all of the Countries with the flag set to False (i.e. Argentina). Instead I get England, Australia, Scotland and none of the countries that are not in the table (the countries table is not comprehensive it just contains the countries that we mail to). Why if it is looking for falses do I get only the records set to True?

            Using this method has its drawbacks: with any substantial set of records it can take a long time to filter the records.

            Any insights?

            Jason

            Comment

              #7
              RE: Export operation won't export

              I can't speak to your exact problem other than to suggest an index be created on the .T./.F. field. This should speed up filtering.
              There can be only one.

              Comment

                #8
                RE: Export operation won't export

                Thanks, I do need to find a way to speed it up and indexes is a good idea.

                I just re-read the documentation (for the 6th or 7th time!) and found the answer on another page that the help file refers to. The "F" does not specify false or true but rather the type of matching the function will use
                (F)irst, (L)ast, or (C)losest match.

                Are there any other speed increasing ideas out there? (not including taking it off the network)

                Jason

                Comment

                  #9
                  RE: Export operation won't export

                  I do not know what tables and fields you have but maybe you could run a join to get a smaller data set, then run some of your other selections on that to make the export. Be sure the join is based on an indexed field, and make the smaller table (e.g. country) is small.

                  Comment

                    #10
                    RE: Export operation won't export

                    Hi, I had a similar problem with a client application where I had to extract up to 30 different data "lists", and selective post codes within those lists. The application is data marketing.

                    I created two extract tables, one for the list numbers, and one for the post codes. Using these to load the intersect criteria, it is easy to extract lists to a list file using the intersect function, and similar with the postcodes. The final operation is to join the two previously intersected files into the final product file.

                    Works quickly, and the users are in control.

                    Should be easy to create a small intersect table to do what you want.

                    Ted G
                    See our Hybrid Option here;
                    https://hybridapps.example-software.com/

                    Apologies to anyone I haven't managed to upset yet.
                    You are held in a queue and I will get to you soon.

                    Comment

                      #11
                      RE: Export operation won't export

                      Could you explain this more to me? I'm not familiar with extract tables and the intersect function. What do they do and how do they work? How do I do a join in Alpha 5? I did them in MS Access about a year ago, but the program set it up for me.

                      Thanks for your help.

                      Jason

                      Comment

                      Previous template Next
                      Working...
                      X