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

Changes to field will not save with the record

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

    Changes to field will not save with the record

    I recently updated to Ver 4.5 build 266 and find it buggy.

    One recent example:
    I just imported a dBase file with a field for social security number. The field did not have "-" separators, so I began changing the field adding in a "-" after the 3rd and 5th numbers (999-99-9999). Once I saved the record or moved onto the next record the field value would revert back to the existing format (999999999).

    1. There are NO field rules in this database
    2. The SSN field has plenty of room (formatted for 50 characters)
    3. I closed the database and reloaded the database. The first SSN record I change can be saved. As I continue making changes to subsequent records, the chages are not saved.

    Ron Wills

    #2
    RE: Changes to field will not save with the record

    Ron,

    Concerning something so simple as this A5 is definitely not buggy so what can be going on?

    You don't have SSN as a numeric field do you?

    But why do you want to store the dashes. You can easily print or otherwise output the contents of the field formatted to include dashes and since they are constants it adds nothing to store them.

    In any layout definition such as a report or form you could define a calculated field with the expression

    left(ssn,3)+"-"+substr(ssn,4,2)+"-"+right(ssn,4)

    and show the result as 999-99-9999

    Bill
    Bill Hanigsberg

    Comment


      #3
      RE: Changes to field will not save with the record

      Ron,

      Another thought:

      You write, "2. The SSN field has plenty of room (formatted for 50 characters) "

      Does this refer to the field witdh on the form's control, the field width in the table definition or both?

      If you increased the number of characters in one but not the other you would have problems with the extra characters.

      Bill

      (I still wouldn't save the dashes but you do want to know what is happening.)
      Bill Hanigsberg

      Comment


        #4
        RE: Changes to field will not save with the record

        Ron,

        One of the great features of this message board is the ability to attach zipped files to a message posted here. Your problem sounds like one that might be easy to unscramble if we can see the whole enchilada. How about sanitizing your data and then attaching a working model here for us to see. Please include a text file or something to tell us how to trigger the issue or problem, written as though we don't know anything about your database... cause we don't.

        -- tom

        Comment


          #5
          RE: Changes to field will not save with the record

          Echoing the kind of advice Tom Cone often gives: Does this happen on the default form as well as custom forms?

          Not sure why you'd define a field for 50 characters when you only need 9 (11 with the dashes). My guess is the field is saved but just not shown. Define the field for the 9 characters you need; similarly design the form to show 9 characters and adjust the display width to show 9 (or a few mort) characters.

          Comment

          Working...
          X