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 of Calc fields

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

    Export of Calc fields

    It should be possible according to the Help file to export calculated fields of a set to an Ascii file. However when I run an operation to export them the set calculated fields do not appear in the field selection. Can any one help as to why they are not appearing in the calc field list in the export genie.
    Tags: None
    #2
    RE: Export of Calc fields

    If by "set calculated fields" you mean fields in one of the tables of a set where the field rules for the field derive the field value from calculations on other fields, they appear as normal fields to any tools (like expression builder). You will find them listed in their normal ordered position as defined in the table structure.

    Calculated fields for a form or a report cannot be exported.

    You could export to a spreadsheet program, perform the calculations, and save the whole to an ascii file if you wanted.
    There can be only one.

    Comment

      #3
      RE: Export of Calc fields

      Many thanks for your reply, in response, the calculated fields I wanted to export were created as Global Calculated fields in the Set, as these were on a combination of fields in both the master table and child tables. It is this combination that I wish to export.
      In the Export card of the export operation these global calculated fields are not included as far as I can see in any of the available field selections, either tables or calculated fields. Does this mean that these Global Calc fields cnnot be exported ?

      Comment

        #4
        RE: Export of Calc fields

        I think you are confusing calculated fields with global variables. I know of no way to create global calculated fields. Fields are parts of tables. Variables are not exportable.
        There can be only one.

        Comment

          #5
          RE: Export of Calc fields

          I tried this a couple of times also, with no success. Global Calculated Fields cannot be used as part of an export operation, except possibly, as part of a filter condition by manually typing in the GCF's name prefixed by CALC->.

          I don't know why A5's export card does not show them, hopefully visability of GCFs, for use in all A5's operations, will be added as an enhancement in a future release.

          I have had success in other operations, where I didn't have visability of them by typing in the GCF's name in the expression builder prefixed by CALC->, but not in an export operation.

          But there is a work around. Add new fields to the tables making up the set, to take the place of the GCF's. Fill the new fields with the values of the GCFs by running an update operation.

          Then do the export.

          Comment

            #6
            RE: Export of Calc fields

            Meant the reply to James' post.

            Stan, what James is referring to are calculated fields created at the table level.

            You create these, while designing your table or set, just like creating any other calculated field.

            You can view any Global Calculated Fields created for a table by clicking on the table's properties.

            Comment

              #7
              RE: Export of Calc fields

              Vince,

              Thanks. I had never used (or seen) those. I'll have to read up on them. Offhand I can't see the purpose. A calculated field in the table is "global" in any place a regular field is available.

              Thanks for the information.

              Stan
              There can be only one.

              Comment

                #8
                RE: Export of Calc fields

                Again many thanks for all your efforts, it seems I have to try another way to get the results of these calculated fields,which are by the way a combination of different fields in both the main and child tables of a set which in alpha 4 v3 (from which I am trying to convert)were set out in the field rules. Now as A5 will not allow child table fields to be used in the default expression data entry field rule of the main table I shall have to rethink.

                Comment

                  #9
                  RE: Export of Calc fields

                  You might be able to do this with either:

                  calculated field rules in the parent table that use lookups to get the values you want from the child tables

                  posting field rules from the child table to the parent with subsequent calculations in the parent

                  redesigning the fields available in the parent vs the child tables
                  There can be only one.

                  Comment

                    #10
                    RE: Export of Calc fields

                    It is unfortunate that this element was so easy to use in A4 as I have made extensive use of this in calculating quite complicated field rules that provide the correct syntax to export data into my accounts programme. The more straight forward numeric calculations can be done by lookups as you suggest, but I have taken in one case 4 different fields from 3 different tables, and I wonder just how many lookup field rules I can add together to produce 1 field to export. I think I am going to have to redesign the main table to include all these child table fields.
                    I really am at a loss as to why Alpha discontinued this facility when it went to Windows, Approach has similar joining of tables as A4 where you can access the other tables in a set with field rules. I am also looking to see if I can write new field rules with XBasic on entry to these fields so as the data can be obtained this way.
                    Regards James
                    I will keep you informed as to whether I m successful or not.

                    Comment

                      #11
                      RE: Export of Calc fields

                      The posts are correct, there is not a way to export calculated fields like we can in Alpha 4. I'm hoping that will be changed/enhanced in version 5.0.
                      To get around the problem, I create a temporary table that has all the info needed, proper field lengths, format, etc and do the export from the temporary table. Runs faster, too.

                      mike
                      Mike Reed
                      Phoenix, AZ

                      Comment

                      Previous template Next
                      Working...
                      X