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

expect blank record

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

    #16
    RE: expect blank record

    Ed,

    Can you copy the app and strip out the tables that aren't needed, perhaps even delete a bunch of records, thus reducing the size of the zip file?

    Jus a thought.

    kenn
    TYVM :) kenn

    Knowing what you can achieve will not become reality until you imagine and explore.

    Comment


      #17
      RE: expect blank record

      Hi,

      Now for something completely different (will apologies to John Cleese):

      Why enter the records through the composite set?

      Why not enter the payments for each member into the transaction record (which, I believe, would be the browse portion of the set)? That way you can just use the member number or last name or a lookup table (looking up the info from the parent record) and enter all the info in a form, skipping the browse all together.

      Regards,

      Jay Talbott
      Jay Talbott
      Lexington, KY

      Comment


        #18
        RE: expect blank record

        Hi Ken,

        I'll give it a shot. Can you explain to me something I don't understand? It is my impression that "sys_send_keys" would activate the keys that are included in the brackets following them. For instance sys_send_keys("{PGDN}"), would activate the PGDN key, and incidently in this case it is close to working with the exception of driving the modem speaker crazy. However; the normal keys to press in order to enter a new record are CTRL-E, which does nothing. Yet when I am in the browse, if I press PGDN, it does nothing.

        Hopefully I can dump the tables without losing data and zip it up to post it on here.

        efs

        Comment


          #19
          RE: expect blank record

          Hi Ken,

          Here it is without data. When the main menu comes up, select Post/ Edit Entries, then Enter/Edit Dues, Enter any dates in the next form and some value of dollars, then click Enter Dues Now. That will take you to a composite form with the member profile at the top and an embedded browse at the bottom. From here when the proper member is selected, press F3 and the defaults entered earlier should appear in a new record at the bottom with the exception of 2 fields that vary from member to member and must be manually entered.

          Not sure how that will work without data in the member table, maybe you can add a phony member for test purposes.

          efs

          Comment


            #20
            RE: expect blank record

            Ed,

            Try attaching the zip again, it didn't take.

            kenn
            TYVM :) kenn

            Knowing what you can achieve will not become reality until you imagine and explore.

            Comment


              #21
              RE: expect blank record

              Hi James,

              The user must see the previous record for each member so she knows the month that the last payment will bring him/her to paid-up.

              efs

              Comment


                #22
                RE: expect blank record

                Hi Ken,

                Here goes ......

                efs

                Comment


                  #23
                  RE: expect blank record

                  Hi Ken,

                  This works but ....... it is incredibly slow and I get long beeps from what i think is the modem speaker.

                  if a_user.key.value = "{F3}"
                  a_user.key.handled=.t.
                  IF a_user.key.event = "down"
                  f=parentform.active()
                  if f="browse1"
                  parentform:numstore.activate()
                  this.fetch_next()
                  else
                  parentform:browse1:datepaid.activate()
                  parentform.allow_change(.T.)
                  ' while isnotblank("datepaid")
                  ' sys_send_keys("{DOWN}")
                  ' end while
                  ' sys_send_keys("{DOWN}")
                  end if
                  end if
                  end if
                  while isnotblank("datepaid")
                  this.fetch_next()
                  end while
                  sys_send_keys("{^E}")

                  Maybe I should go back to laser design, at least I understood that !

                  efs

                  Comment


                    #24
                    RE: expect blank record

                    Hi Stan,

                    All of the references I see to .new_record are followed by lines in the code that set fields to specified values in ensuing coding. I don't see any reference to allowing keyboard input to a field with the focus. Hence, I have been trying to use sys_send_keys("{^E}")and variations of the characters in the curly brackets. The closest I have is when that statement is outside of the if statements, although that works in part it slows down to a crawl and drives the sonalert on the modem crazy. I can in all cases press CTRL-E and then enter a new record. Following is the code that I have been working with, you can see some of the things that I have tried and remarked out. Any more hints?

                    if a_user.key.value = "{F3}"
                    a_user.key.handled=.t.
                    IF a_user.key.event = "down"
                    f=parentform.active()
                    if f="browse1"
                    parentform:numstore.activate()
                    :parent.fetch_next()
                    else
                    parentform:browse1:datepaid.activate()
                    parentform.allow_change(.T.)
                    :parentfrom.fetch_first()
                    while isnotblank("datepaid")
                    :parentform.fetch_next()
                    end while
                    sys_send_keys("{PGDN}")
                    end if
                    end if
                    end if
                    ' while isnotblank("datepaid")
                    ' sys_send_keys("{DOWN}")
                    ' this.fetch_next()
                    ' end while
                    ' sys_send_keys("{CTRL-E}")
                    ' :parentform.new_record()

                    Thank you for any help in advance,
                    efs

                    Comment


                      #25
                      RE: expect blank record

                      From the docs --- Every object in Alpha Five has a collection of methods that let you manipulate the object, or
                      find out information about that object. For example, a form has a new_record() method that
                      adds a new record to the form.
                      Xbasic allows you to call the methods of an object. For example, assume you have a form
                      called �Customer�. To add a new record to this form, you would use this Xbasic statement:
                      :Customer.new_record() addressing the form by name or parentform.new_record() not ":parentform".

                      The examples shown are also demonstrating that once the new record is created you can begin filling in fields with known values.

                      They also show some code to activate one of the form fields to await data entry, which you don't seem to be emulating.


                      No clue as to why you're having the speaker noises.

                      Stan
                      There can be only one.

                      Comment


                        #26
                        RE: expect blank record

                        Hi Stan,

                        Thank you for responding. I have tried the following code without success. The sys_send_keys has been added and remarked out.

                        if a_user.key.value = "{F3}"
                        a_user.key.handled=.t.
                        IF a_user.key.event = "down"
                        f=parentform.active()
                        if f="browse1"
                        parentform:numstore.activate()
                        parentform.fetch_next()
                        else
                        parentform:browse1:datepaid.activate()
                        parentform.allow_change(.T.)
                        :browse1.new_record()
                        ' sys_send_keys("{^E}")
                        end if
                        end if
                        end if

                        Could F3 be interfering with the innards of A5?

                        Thank you,
                        efs

                        Comment


                          #27
                          RE: expect blank record

                          Try this, still has problems but they may be with your table level field rules or from restrictions.

                          if a_user.key.value = "{F3}"
                          a_user.key.handled=.t.
                          IF a_user.key.event = "down"
                          f=parentform.active()
                          if f="browse1"
                          parentform.fetch_next()
                          else
                          parentform.allow_change(.T.)
                          :browse1.new_record()
                          :browse1:datepaid.activate()
                          end if
                          end if
                          There can be only one.

                          Comment


                            #28
                            RE: expect blank record

                            Hi Stan,

                            I added another end if at the end but it is still stubborn. With this code, it won't switch to the embedded browse (browse1)

                            Again, thanks for all of your time,
                            efs

                            Comment


                              #29
                              RE: expect blank record

                              BTW, all restrictions are removed. It might be noteworthy to point out that of the 6 fields in the embedded browse, 4 of them are calculated fields set by ask variables in the previous form, the first 3 and the 6th. The reason for this is when she enters about 800 records, most of them contain the same data, it makes entry much quicker. AND ....... I can easily enter a new record if I press CTRL-E. I am just trying to speed up her process. In my original code the procedure was to set 4 defaults on a form with ask variables, press a button to go to the composite form, press F3 to go to the embedded browse, press enter 3 times enter $values in the next 2 fields, press enter, press F3 twice and then repeat for each member. Everything works great except it doesn't go into "enter new record", instead of pressing F3 twice and pressing enter 3 times etc, I have to press CTRL-E after pressing F3 twice, it's the CTRL-E I am trying to eliminate.

                              Thanks a bunch
                              efs

                              Comment


                                #30
                                RE: expect blank record

                                Let's loose some more colons.

                                if a_user.key.value = "{F2}"
                                a_user.key.handled=.t.
                                IF a_user.key.event = "down"
                                f=parentform.active()
                                if f="browse1"
                                parentform:numstore.activate()
                                parentform.fetch_next()
                                browse1.new_record()
                                browse1:datepaid.activate()
                                else
                                parentform.allow_change(.T.)
                                Browse1.Activate()
                                browse1.new_record()
                                browse1:datepaid.activate()
                                end if
                                end if
                                end if

                                This will still need modification if I don't have your intent correct.

                                Stan
                                There can be only one.

                                Comment

                                Working...
                                X