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

Synchronize w/ 2nd form

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

    Synchronize w/ 2nd form

    I don't find a code snippet for this simple case since I am usually going between diffreent tables. I need code on a button to open a 2nd form from the current table, and synchronize to the record on the current form.

    This is easy if I code in the table name, but I want it generic, without a hard coded reference to a table name. Can't use Query() generated by the button genie since all records must show. #2 is where I need help
    1. get form pointer for new form that is loaded.
    2. fetch_goto() the recno that is same as current form

    the command would be
    f:Tables:my_table_name.fetch_goto(my_var)

    But I don't want to hard code "my_table_name". Working with xbasic explorer,I have not come up with the right syntax that generalizes this command. It will only be used on tables, not sets, so there will be only 1 table for the form.

    Bill.

    #2
    RE: Synchronize w/ 2nd form

    Bill, have you considered adding the other fields to your present form and hiding them while working with the first 'view'... then hiding the first group of fields and showing the second, at the press of a button when you want the 'view' to change. This would save opening a second instance of your table and you wouldn't need to synchronize two forms.

    While not well known it's easy to position fields right on top of each other. Hide one, show two. Then hide two, show one.

    -- tom

    Comment


      #3
      RE: Synchronize w/ 2nd form

      Problem solved. Use
      f:Tables.child(1).fetch_goto(vRecnum)

      Bill.

      Comment


        #4
        RE: Synchronize w/ 2nd form

        Tom,

        This a huge table (800 fields), so maintainability in separate forms is very important.

        Bill.

        Comment


          #5
          RE: Synchronize w/ 2nd form

          Bill,

          That's probably the wrong technique to use. The child(1)is the last link of a table. If anything, you want to reference from the 1st table (the parent) which is the last child(n) where n can be gotten from the children() method. So it would be something like child(children()-constant). But assuming you always want that table independent of where it is in the parent, then easiest way is to create an object like (I haven't checked the syntax)

          formname=table.current().name_get()
          tbl=obj(formname+":Tables:"+my_table_name)
          tbl.fetch_goto(my_var)

          Regards,

          Ira J. Perlow
          Computer Systems Design & Associates
          [email protected]
          Regards,

          Ira J. Perlow
          Computer Systems Design


          CSDA A5 Products
          New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
          CSDA Barcode Functions

          CSDA Code Utility
          CSDA Screen Capture


          Comment


            #6
            RE: Synchronize w/ 2nd form

            Ira,

            I had never investigated to see that the parent was always in the child(children()) position. That is good info. This technique will be for multiple forms on the same flat table, so children()=1. To always apply to the parent table if it were a set, command could be
            f:Tables.child(children()).fetch_goto(vRecno).

            The reason I wanted to do it this way is that code does not change when it is used for dofferent forms/tables (as long as it is parent). So you can use button genie to open the form and paste in the standard synchronization code which does not need to know a table or form name.

            If the 2nd form is on a _different_ table, then a query technique must be used. That is what I normally do, and it needs to be customized for each situation. I far prefer having standard code I can paste in.

            Bill.

            Comment


              #7
              RE: Synchronize w/ 2nd form

              Bill,

              when you have the same record viewed on different forms, presumably, with an 800 field record, so that you could give the user access to different groups of fields depending on what they are doing, and the user is changing data on the same record on these different forms, - when the user leaves, and I guess closes a form, to go to another one, do you exit the form without "saving the record", or does it make any difference - what I'm wondering is how you can do this. I really like the idea - since a lot of editing I do is on a single table.
              Cole Custom Programming - Terrell, Texas
              972 524 8714
              [email protected]

              ____________________
              "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

              Comment


                #8
                RE: Synchronize w/ 2nd form

                A record can have only one data entry processing going against it at a time. If another form, script, etc. tries to change the record, it is told the record is locked. So having multiple forms does not change that restriction.

                In my case, data entry is done on one form (with 15 tabs) and other forms display the data with different calculations, groupings, etc.

                Bill.

                Comment

                Working...
                X