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

Prevent Changes on Form

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

    Prevent Changes on Form

    I have a form, based on a set. Staff.dbf is the parent and visits.dbf is an embedded browse.

    I want to prevent changes (new records or changes) to the parent (staff.dbf), but permit changes and new records to be entered into the browse1.table (visits.dbf).

    Suggestions would be very much appreciated.

    seems the following code should go somewhere! Probably pretty obvious - but don't worry about embarrassing me.

    cancel()
    ui_msg_box("changes not allowed","Click on table below to make changes")

    Thanks

    Tom

    #2
    RE: Prevent Changes on Form

    Tom,

    Why not just set the properties of any object on the form that refers to the parent to readonly or even disable? The user can't access the field to change it.

    Jerry

    Comment


      #3
      RE: Prevent Changes on Form

      Jerry,

      Good Morning

      I've done as you suggested, I only have a calculated field based on the Parent on the form, but when I click on the toolbars * add record button, a new record is formed, or the at least the calculated field (fullname = Lname+", " + Fname)shows only the ", ".

      I guess I'd like the add new record button to be disabled unless the Browse1 was active.

      Suggestions

      and TIA

      Tom

      Comment


        #4
        RE: Prevent Changes on Form

        I still haven't figured this problem out.

        Other suggestions would be appreciated.

        Tom

        Comment


          #5
          RE: Prevent Changes on Form

          Open the form in design mode,
          Main Menu/Form/Properties
          Check the Restrict Enter and Change boxes.

          This will prevent new records being added or changed in the parent, but you can still click the "New Record" line in the embedded browse to add child records.

          Finian
          Finian

          Comment


            #6
            RE: Prevent Changes on Form

            Finian,

            Thanks a bunch - you were right, not surprisingly. I though it would prevent changes on the entire form.

            One more question - why doesn't the following work?

            if isblank(":Daily_Productivity:Browse1:Payor" Then
            :Daily_Productivity:Browse1:Patient.font.color = "Red",
            Else
            :Daily_Productivity:Browse1:Patient.font.color = "Black"
            end if
            end

            I get the error, ...Payor not found I tried Payor.text and Payor.value and still not luck. This is on a form's oninitiate event.

            Thanks

            Tom

            Comment


              #7
              RE: Prevent Changes on Form

              isblank(":Daily_Productivity:Browse1:Payor" refers to a field object. The isblank() command works with field values. Try:

              tbl = table.current()
              if isblank(tbl.payor) 'assuming Payor is a field, not merely an object name
              Browse1:Patient.font.color = "Red",
              Else
              Browse1:Patient.font.color = "Black"
              end if
              Peter
              AlphaBase Solutions, LLC

              [email protected]
              https://www.alphabasesolutions.com


              Comment


                #8
                RE: Prevent Changes on Form

                should be:

                if isblank("tbl.payor")
                Peter
                AlphaBase Solutions, LLC

                [email protected]
                https://www.alphabasesolutions.com


                Comment


                  #9
                  RE: Prevent Changes on Form

                  It still doesn't work. The field "Payor" is in Browse1.

                  I tried, the following, without success -

                  tbl = table.current(2) '(2)to designate browse1
                  if isblank("tbl.payor") then 'Payor is a field, in browse1
                  Browse1:Patient.font.color = "Red"
                  Else
                  Browse1:Patient.font.color = "Black"
                  end if

                  The above, results in all Patient names in red, I only want the patient name in red if payor is blank.

                  More suggestions please.

                  Tom

                  Comment


                    #10
                    RE: Prevent Changes on Form

                    Thomas,

                    If the field "payor" was on the form instead of in the browse, you could set the font color for the field "box" to change as you wish. Since it is in the browse, you are setting the font color for the column ("payor") of the browse.

                    I'll take a look at learn alpha.com. I think I remember something about changing the color of a "row". This could serve the purpose you want.

                    Stan
                    There can be only one.

                    Comment


                      #11
                      RE: Prevent Changes on Form

                      Here is a link to the article I remembered. You might be able to alter the code to fit your needs.
                      There can be only one.

                      Comment


                        #12
                        RE: Prevent Changes on Form

                        Stan,

                        Thanks for the reference, it was the answer. Your memory is alot better than mine. I have read all the articles on Dr. Wayne's site, but forgot this one. Thanks.

                        If I may ask one more question - always another. Why do you suppose this code doesn't work.

                        :Daily_Productivity:Browse1.Index_Set("inv_date")
                        :Daily_Productivity:Browse1.Fetch_First()
                        :Daily_Productivity:Browse1.Resynch()
                        end

                        Is there a problem when inverting dates, then fetch_first?

                        Thanks

                        Tom

                        Comment

                        Working...
                        X