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

Truncating XBasic code

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

    Truncating XBasic code

    In trying to create an inline XBasic action script of about 35 lines, I type the script completely, test the syntax (F4), and proceed through Finish. When I go back to the script, it's truncated at line 29.

    Any idea why this is happening and how I get past it? Thanks.

    #2
    RE: Truncating XBasic code

    Ed,

    Inline XBasic action scripts are notorious for being able to hold very little code in them. Often, as you have observed, they will appear to be handling it all -- especially if you paste some code in, but when you look inside the code window a second time, you find that the script is truncated. I have wrestled with this many times, but there iis a simple solution!

    You simply creaste a series of XBasic action scripts which are logically segmented pieces of your one, larger block of code.

    NOTE: They must be in seqiuential order when displayed in the action script window; in tree form. Also, you can't put "END" at the end of any of your scripts, except the last in the series; or else the precession will stop there, rather than continuing on to the next script(s) in line.

    Hope this helps.

    Regards,

    Geoff Hollander

    Comment


      #3
      RE: Truncating XBasic code

      Ed:
      Instead of using in-line xbasic, convert to xbasic and you will have a lot more room.
      Charlie crimmel

      Comment


        #4
        RE: Truncating XBasic code

        Thanks for the quick response. I set the following up as XBasic code. In executing it, I get the following error message...

        Script"History_hours line:30
        a_tbl.append()
        Variable append.m_key references a non-existant field SEQ

        "History_hours" is the db to which I want to append data from "Riding_Hours", and both contain the same fields/field names including SEQ.

        I'm obviously doing something wrong. Any idea what?

        BTW, I pasted the append code from the Script recorder window after I ran the append from the control panel. I've highlighted with an * (asterisk) the lines I changed/added.


        *dim throughdate as d
        *dim sathroughdate as c
        *sathroughdate=ui_get_date("DELETE DATE", "Through What Date ",dtoc(throughdate))
        *throughdate=ctod(sathroughdate)
        *table.open("C:program filesa5v4Sign_In_Outhistory_hours.dbf")
        a_tbl = table.current()
        append.t_db = "c:program filesa5v4 sign_in_outriding_hours.dbf"
        append.m_key = "SEQ"
        append.t_key = "SEQ"
        append.m_filter = ""
        *append.t_filter = "RidingdateSEQ"
        append.m_field2 = "FULLNAME"
        append.m_exp2 = "@RIDING_HOURS->FULLNAME"
        append.m_field3 = "RIDINGDATE"
        append.m_exp3 = "@RIDING_HOURS->RIDINGDATE"
        append.m_field4 = "ROSTER_HOURS"
        append.m_exp4 = "@RIDING_HOURS->ROSTER_HOURS"
        append.m_field5 = "PAGER_HOURS"
        append.m_exp5 = "@RIDING_HOURS->PAGER_HOURS"
        append.m_field6 = "SAC_HOURS"
        append.m_exp6 = "@RIDING_HOURS->SAC_HOURS"
        append.m_field7 = "REASON"
        append.m_exp7 = "@RIDING_HOURS->REASON"
        append.m_field8 = "IDENT"
        append.m_exp8 = "@RIDING_HOURS->IDENT"
        append.t_count = 0
        a_tbl.append()

        Comment


          #5
          RE: Truncating XBasic code

          Ed:
          I just changed these 3 lines
          try it and let me know
          You might have to post your files so we could take a closer look
          Charlie Crimmel

          tbl=table.open("C:program filesa5v4Sign_In_Outhistory_hours.dbf")
          append.m_key = ""
          append.t_key = ""

          Comment


            #6
            RE: Truncating XBasic code

            Ed:
            I dont think that last post will work.
            You will probably have to use pointers to the different tables.
            If both tables have SEQ , it might be getting confused.
            see if you can post your files so we can take a closer look.
            Charlie Crimmel

            Comment


              #7
              RE: Truncating XBasic code

              Charlie:

              Attached are the files in question.

              Realy appreciate your help.

              Ed

              Comment


                #8
                RE: Truncating XBasic code

                Many thanx, Geoffrey.

                Comment


                  #9
                  RE: Truncating XBasic code

                  you have set a_tbl to table.current(), but i think
                  you mean to set it to the table you explicitly open
                  and append records to.
                  e.g.
                  a_tbl=table.open("C:program files|a5v4|Sign_In_Outhistory_hours.dbf")

                  Comment


                    #10
                    RE: Truncating XBasic code

                    Thank you, Dr. Wayne. Works perfectly now.

                    Ed

                    Comment

                    Working...
                    X