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

Allow edits

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

    Allow edits

    Hi Phorum,

    I have a 1 to many set of members/dues (members is the parent). I have a form to enter dues which has the members name and an embedded browse of the selected columns for entering dues into the dues table each month for the corresponding member. The user has infomed me that she makes typos upon entering data (which is expected), but the embedded browse will not allow edits. Allow edits has been checked. I also have a copy of a data entry form from Tom Cone that has this problem solved with a change button on the form, the script on that form looks like this:

    this.disable() 'prevent dble click from running script twice
    parentform.restrict_change = .f.
    parentform.restrict_navigation = .t.
    parentform:idnum.activate() 'set focus

    'hide closeform button, show cancel and save
    parentform:cancelchanges.show()
    parentform:savechanges.show()
    parentform:closeform.hide()

    ' disable other controls
    parentform:newrecord.disable()
    parentform:deleterecord.disable()

    For my case I changed idnum to "lastname", hence the focus works.but ......
    I get an error when i click that button and am still not allowed to make a change to an existing record in the chid (dues) table.

    Any ideas?

    Ed Schulz
    Edwards Consulting

    #2
    RE: Allow edits

    Ed,

    It is just possible that you are confusing "allow edits" for the form and "allow edits" for the embedded browse. Setting this property for the form will not control what you can and cannot do in the browse.

    Tom's code controls the allow_edits property of the*form*.

    "The user has infomed me that she makes typos upon entering data (which is expected)" I'm assuming she is not entering the data in the browse.

    "but the embedded browse will not allow edits" but she wants to correct the typo there because it's convenient.

    "Allow edits has been checked." Where?

    Bill
    Bill Hanigsberg

    Comment


      #3
      RE: Allow edits

      browses have a browse.readonly property, akin to
      the form's restrict_edit and restrict_change property.
      if you want to set a browse to read-only, your button
      should read


      Browse1.browse.readonly=.t.

      to make it editable, you write
      Browse1.browse.readonly=.f.

      (assuming the browse is named Browse1)

      Comment


        #4
        RE: Allow edits

        Thank you Bill, I'll go check now, but i think i set "allow edits in the browse"

        Thanks again,
        Ed

        Comment


          #5
          RE: Allow edits

          WoW, that's new to me. Thanks a million Dr. Wayne, I won't forget this.

          Thanks again,
          Ed

          Comment


            #6
            RE: Allow edits

            Hi Dr. Wayne,

            The name of my embedded browse is "dues_entry_new", so I put a line in the onpush of the button to bring up the form that reads "dues_entry_new.browse.readonly=.f." (without the quotes) .......... but, it still won't allow edits. I double checked the browse properties and allow change is not restricted.

            Comment


              #7
              RE: Allow edits

              you say you put the line in the OnPush of the button that
              brings up the form. that makes it sound to me as though the
              script is on a different form. in that case, alpha five can't
              find the dues_entry_new browse without more specification of
              the object, e.g.

              f=form.load("new form")
              f.restrict_change=.f.
              f.restrict_enter=.f.
              f:dues_entry_new.browse.readonly=.f.
              f.show()
              f.activate()

              Comment


                #8
                RE: Allow edits

                Hello Dr. Wayne,

                Thank you for your input, obviously I am somewhat of a newbie to xbasic. I'll insert your coding immediately and try again. What I had not mentioned before is that of the 6 fields where data is entered, 4 of them are variables where the defaults are entered in a previous form, the remaining 2 are editable.

                Thank you again, I am LEARNING,
                Ed Schulz

                Comment


                  #9
                  RE: Allow edits

                  Hi Dr. Wayne,
                  I copied and inserted your coding in "onpush" of the form for entering data. When I click the button, I get "command inline Xasic, Error: object method error.A parameter may be incorrect or misspelled". Here is what is on the button:

                  f=form.load("dues_entry_new")
                  f.restrict_change=.f.
                  f.restrict_enter=.f.
                  f:dues_entry_new.browse.readonly=.f.
                  f.show()
                  f.activate()
                  Many thanks again for your valuable time,
                  Ed Schulz

                  Comment

                  Working...
                  X