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

Pasting expressions into calc fields via script.

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

    Pasting expressions into calc fields via script.

    One reason I have avoided converting some old A4 applications to A5 is the reports. On the plus side, the reports in A5 would be 99% identical in design. As far as I can tell, about all of the functions are the same except lookup functions, which are easy to adjust. On the minus side is that we have some complicated reporting requirements and most reports in these old applications involve A LOT of calculated fields. Some of these fields have expressions are about as long as the maximum limit on expressions. Every time I think of retyping all these calculated fields in A5 without making any mistakes I curl up under my desk and whimper.

    I'm trying to figure out a way to input the calculated field names and expressions from a table. It has been fairly easy to take one report with 253 calculated fields and cut/paste them into a text file, then import them into a table. I think I can work this out by fetching records, recording keystrokes, and copying and pasting the contents of the table fields into the Calculated Fields window via clipboard commands. However, I'm stuck when it comes launching this script. I'm in the form's design mode and have the Calculated Field window active. How do I get my script going to fill in the calculated field names and expressions?

    Any advice or ideas would be greatly appreciated.

    #2
    RE: Pasting expressions into calc fields via scrip

    Richard,

    I don't think you need to automate this in this manner. Have you tried pasting the calculated field names and definitions to a spread sheet file rather than a text file.

    From a spreadsheet file you should be able to paste back into the calculated field dialog box "en masse".

    I routinely copy calculated fields out of Alpha to a spread sheet file, perform search and replace functions, and paste back in to Alpha.
    There can be only one.

    Comment


      #3
      RE: Pasting expressions into calc fields via scrip

      Stan,

      When coying/pasting from the spreadsheet, I assume you mean one calculated field at a time, not copying a range of cells and then pasting this into the Calculated Fields window. I tried your suggestion but could not copy and paste reliably from Excel to the A5 window. I could from a text file, one field at a time, first the calc field name, then the expression. I think the problem with Excel and A5 is likely a Windows NT issue. I kept getting "clipboard full"-type messages.

      I have so many fields with similar names and expressions that I was hoping to automate the process to avoid getting lost and confused (a frequent state on my part). Such a script could be used for other reports as well.If worst comes to worst I will copy and paste from a text file, at least.

      Thanks.

      Comment


        #4
        RE: Pasting expressions into calc fields via scrip

        Nope.

        Depends on where you are but, for instance, in a table you can select the box to the left of a record, drag down as many rows as you like, ctrl+c to copy, switch to spread sheet, select a cell, and paste. Each field in each record should paste into a separate cell.

        If your table holds your calculated fields names and definitions, then when your changes are made you go back to the calculated field dialog and paste into the top left empty cell. Field names and definitions should "flow" into the proper boxes.
        There can be only one.

        Comment


          #5
          RE: Pasting expressions into calc fields via scrip

          Stan,

          Your suggestion worked just fine when copying from my table. It took me a few tries to get the correct "paste" to work (menu, right-click menu, ctrl-v...). For me, it turned out to be the Paste button on the right side of the calc fields dialog window. I had given up trying to use those buttons in version 3 since they never seemed to work. Anyway, this worked and is much better than trying to do it via a script. It is easy to convert this stuff between tables, text files, or a spreadsheet. Since I know copying from a table works, I'll convert from a spreadsheet or text file to a table when doing this again.

          Thanks again. Now I have no excuse to avoid converting these apps.

          Comment


            #6
            RE: Pasting expressions into calc fields via scrip

            Sorry, I should have made it more difficult. How about a broken finger, that would be a good excuse.
            There can be only one.

            Comment

            Working...
            X