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



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

Calendar field type

  • Filter
  • Time
  • Show
Clear All
new posts

  • Calendar field type

    I have a form, based on a set and in design view I keep setting Properties>Field Type to 'calendar' for a date field. It works fine for that session but when I reopen the form, the field type some times has reverted back to 'type-in field'.
    I did not find any reference to previous postings searching on 'calendar'
    Will appreciate help.

  • #2
    RE: Calendar field type

    Have you explicitly saved the form after setting the field properties? That is, you must agree to the change (ok or save) in field properties and *then* save the whole layout.

    Bill Hanigsberg


    • #3
      RE: Calendar field type


      Yes, I was careful to save after any changes.

      The 'calendar' field type works ok for a while then it reverts back to 'type-in field' but I don't know when. I know this seems nonsensical but it's happening.


      • #4
        RE: Calendar field type

        I will try to explain what I found after spending a lot of time trying to isolate the problem.

        I set my date field type to 'calendar', save the form, switch to form view and check the date field. It properly shows the calendar.
        I close the form, re-open it in design view, add a text field to force a need for save. I then switch to form view, check the date field, it's ok. I close the form and A5 asks if I want to save (referring to the text field that I added), I click 'yes'.
        I re-open the form in view and the date field has reverted to 'type-in field'.


        • #5
          RE: Calendar field type

          I don't know if this relates to the same problem or not, but it sounds similar to a problem that I have, and that I reported a few days ago in another thread. I have a form in which I have previously saved custom menu and toolbars. I then want to change these to a different menu and toolbar. I go into Properties, make the change, save it, close the form, and then go back in and the values revert back to original menu and toolbar.

          Has anyone experienced this?

          Gary Traub
          Gary S. Traub, Ph.D.


          • #6
            RE: Calendar field type

            I am having the same problem. The Calendar field reverts back to Type-in. I thought my memory had failed and I had not set the field to Calendar. I am also experiencing the same problem with the calculator field.


            • #7
              RE: Calendar field type

              i can confirm the issue and i'm sure alpha will fix it now that neil has so clearly isolated it. in the meantime, the workaround is simple--just explicitly save the form before switching to form view after you add a new field or object to your form.


              • #8
                Re: Calendar field type

                I realize that is is a very old post, but I have encountered the same issue as posted by Neil Terry in Alpha Anywhere V12. Has this bug been addressed?