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

Modifying applications once they are done.

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

    #16
    Re: Modifying applications once they are done.

    Cal,
    That was my thought, also. Here's my table structure. According to the datapath variable, it is looking at the same table I'm looking at. I'm thinking of sending in a bug report to see if I can get a response there. Let me zip up a small app with the table in it and I'll send it to you.
    Ernie

    Comment


      #17
      Re: Modifying applications once they are done.

      Cal,

      I don't believe that would cause the error. When I experimented last night, if one or more of the fields already exists then the function

      table.Add_Fields()

      just adds a field with a number tacked on the end like

      Total_Charges0
      Pctdep_Req0
      Dep_Req0

      I did not test to see what happen if those fields already existed.
      There can be only one.

      Comment


        #18
        Re: Modifying applications once they are done.

        Cal,
        Here's a small example. One table and one script. Hope it comes thru OK.
        Ernie

        P.S. I went back to the a5_add_fields_to_table() because it seems the table.add_fields() function is just a wrapper. In the script error, I would get a reference to a5_add_fields_to_table() when using table.add_fields().

        Comment


          #19
          Re: Modifying applications once they are done.

          Ernie, I think you're misusing the escape character.

          Later:

          Ernie, I was mistaken. It turns out you don't need to escape the backslash if the backslash is included with other characters.

          Compare:

          Code:
          myVar = a5.get_path()
          myVar = myVar + [COLOR="Red"]"\\"   'no other chars in the string[/COLOR]
          ?myVar
          = "C:\A5v9_databases\For_James_M\"
          myvar = myVar + "Filename.dbf"
          ?myVar
          = "C:\A5v9_databases\For_James_M\Filename.dbf"
          With the following:
          Code:
          myVar = a5.get_path()
          myvar = myVar + [COLOR="Red"]"\Filename.dbf"    'other chars are present in the string[/COLOR]
          ?myVar
          = "C:\A5v9_databases\For_James_M\Filename.dbf"
          Last edited by Tom Cone Jr; 06-03-2008, 10:16 AM.

          Comment


            #20
            Re: Modifying applications once they are done.

            The problem seems to be with the two short time fields. Removing them lets the script function. Changing them to time fields allows the script to run.


            This might be a bug if anyone can confirm.
            Last edited by Stan Mathews; 06-03-2008, 09:49 AM.
            There can be only one.

            Comment


              #21
              Re: Modifying applications once they are done.

              Tom,
              This is the code in the zip file.
              Code:
              fields = <<%str%
              Total_Charges,N,10,2
              Pctdep_Req,N,3,0
              Dep_Req,N,10,2
              %str%
              a5_add_fields_to_table("reservations",fields)
              Ernie

              P.S. Stan, in stepping thru the code with debug, it gets passed the time fields with no problem.

              Comment


                #22
                Re: Modifying applications once they are done.

                Please explain to me how you are stepping through the code behind the line

                a5_add_fields_to_table("reservations",fields)

                I believe it is the internal working of this function that is choking on the time fields.

                Duplicate the reservations table, remove the short time fields, change the script to refer to the duplicated table. It should then run and add the fields to the duplicated table.
                There can be only one.

                Comment


                  #23
                  Re: Modifying applications once they are done.

                  Stan,
                  I just put the debug(1) at the beginning of the script and when it gets to the a5_add_fields..... line, it goes to the template and steps thru each field. I know that's not the whole template, but....
                  Ernie

                  Comment


                    #24
                    Re: Modifying applications once they are done.

                    Thanks, never saw that before.

                    I still think the short time fields are causing the problem. The lines like

                    append.m_exp1 = ....

                    merely set up the append variables needed later. It is when those variables are used in the final statement using them that the issue surfaces, I think.

                    Did you test my suggestion? - Edit, I see that you did from your thread in V9.
                    There can be only one.

                    Comment


                      #25
                      Re: Modifying applications once they are done.

                      Thanks for the help, Stan. Yes I did submit a bug report. I might try changing it to just a time stamp field. Seems a5 has some problems with time fields. I've had trouble with field rule drop boxes, time fields in the calendar addon and now this.
                      Thanks again.
                      Ernie

                      P.S. Selwyn did find a bug. It has been fixed and will be in the next update.

                      Comment


                        #26
                        Re: Modifying applications once they are done.

                        Originally posted by enstorms View Post
                        P.S. Selwyn did find a bug. It has been fixed and will be in the next update.
                        Of which version(s). You posted first in V7. It also happens in v8.
                        There can be only one.

                        Comment


                          #27
                          Re: Modifying applications once they are done.

                          Glad you guys handled this. I've been busy and haven't read e-mail or looked at the message board all day.

                          AND:
                          Originally posted by Stan Mathews View Post
                          ... if one or more of the fields already exists then the function

                          table.Add_Fields()

                          just adds a field with a number tacked on the end like

                          Total_Charges0
                          Pctdep_Req0
                          Dep_Req0

                          I did not test to see what happen if those fields already existed.
                          Duhhh. I knew that - don't know why I forgot it when I wrote that post. Also, another try will produce fields ending in 1 then 2 then 3 then 4 then 5 then 6 then 7 ... then 21. (Does that perhaps sound like the voice of experience?:D I once mistyped the field name in the IF line and it just kept recreating the new field with the next number on the end.)

                          Comment


                            #28
                            Re: Modifying applications once they are done.

                            Stan,
                            I posted the bug from v9.
                            Ernie

                            Comment

                            Working...
                            X