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

Form values clear when pressing save!

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

    Form values clear when pressing save!

    Hi Folks,
    Attached is a small table with a simple form. If you open the form,click the "enter a new record" button, fill in the form then click the "save record" button on the toolbar it saves. Great no problems!. However if you try this again, when you click "save", all the data you just typed in on the form vanishes!
    If you remove the "fault category","engineer" and "assigned by" record list edit combo boxes it works fine. Im assuming its something to do with these but I cant see the solution.
    Can anyone help?
    Thanks
    Steve

    #2
    Re: Form values clear when pressing save!

    Perhaps others will clarify or correct me, but I don't think you should use the record-list comb box object to display field values from the current table supporting your form. In cases where you have a relatively small number of choices and they are fixed in the app, a simple list lookup field rule is a better choice. Otherwise, a table lookup field rule is better. Personally, I prefer to keep my lookup lists in separate tables, rather than build the lookup lists from the current table.

    Interestingly, your form seems to work fine in A5v7. Perhaps the trouble you're having was corrected somewhere along the way... can't say.

    -- tom
    Last edited by Tom Cone Jr; 08-04-2006, 11:11 AM.

    Comment


      #3
      Re: Form values clear when pressing save!

      Steve,
      A few things have to be corrected but is simple enough to do.

      1. It seemed that your fault category fields were overlapping and read only - separated them and unchecked the read only--you can have this field skipped if need be in the field rules.

      2. Some fields were beyond the form width on the right side and had to shorten them.

      The above cured half the problems but then found out the main reason I feel you were having problems (which could mean the above did very little but should be corrected anyway I feel).

      3. Not only was the length of your table and form name very long they were very similar---so I duplicated your table, copied your form to this new table....and then shortened the names to 10 characters each and made them different after the 4th character.

      Form saving worked ten times in a row with all fields filled in after I did this so think it should work for you.

      ---thought the long and similar names mainly applied to form vs form and table vs table..?? Apparently Alpha can get confused between tables and forms as well if named similarly or maybe it was just the long names.

      Someone with more knowledge please clarify this for everyone please!


      Mike
      Last edited by MikeC; 08-05-2006, 12:33 AM.
      Mike
      __________________________________________
      It is only when we forget all our learning that we begin to know.
      It's not what you look at that matters, it's what you see.
      Henry David Thoreau
      __________________________________________



      Comment


        #4
        Re: Form values clear when pressing save!

        Mike, thanks for taking a look. My own diagnosis appears to have been off the mark, so I'm glad you pitched in.

        A very good practice is to keep table and fieldnames (and indextag names) to 10 characters or less; and to not use blank spaces anywhere in a name. Use the hard underscore instead. So, "Property Maintenance" would become "Prop_Maint".

        I saw two other things in Steve's sample that warrant comment, especially if he's just getting acquainted with Alpha Five.

        1) the only index on his table is set to include "Unique Only" entries. This option is rarely used in Alpha Five and should never be used to try to prevent the entry of records with duplicate primary keys. All this will do is suppress the display of records with duplicate keys. It does not validate new or changed records to assure uniqueness. This is different from what similar settings in other databases would do.

        2) Steve stored his table in a different folder than his database. This severely restricts portability and is rarely advisable. When we opened his database we could not open his table or see his form because the path to the table and its dictionaries on our machines is different from the path he's using on his machine. These "pathing" issues go away and databases become portable regardless of drive and folder names simply by storing the tables in the same folder as the database dictionaries. (i.e. in the same folder as the ADB file for his dictionary).

        -- tom

        Comment


          #5
          Re: Form values clear when pressing save!

          Many thanks for taking the time to reply guys. Lots of useful info there which Ill be using to adjust our databases.
          Thanks
          Steve

          Comment

          Working...
          X