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

A friendly word of warning about the date 01/01/2020

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

  • A friendly word of warning about the date 01/01/2020

    We run a car club here, and have members renewing all the time. Since normal membership is for one year, we now have memberships expiring on 01/31/2020.
    If, however, you write 01/31/20, Alpha assumes this is 1920, not 2020.
    This is because in View | Settings | Date, there is a text box in the "Two digit dates between 00 and [ 20 ] are assumed to be int he 21st century."

    You can change the 20 to 50, or what ever suits you, to avoid this problem.

    Hope this helps someone.

    Jay
    Jay Talbott
    Lexington, KY


  • #2
    Re: A friendly word of warning about the date 01/01/2020

    Nice catch Jay!
    Glen Schild



    My Blog

    Comment


    • #3
      Re: A friendly word of warning about the date 01/01/2020

      Is there a way to change this setting using xbasic? I have about 30 computers using the runtime that will need to be changed. Really don't want to have to sit down at each one to change this setting.
      Alpha Anywhere v3.5
      Version 12.3, Build 2999
      MySql56 & DBF's

      Alpha 4, 5, Anywhere

      Ron Anusiewicz

      Comment


      • #4
        Re: A friendly word of warning about the date 01/01/2020

        Originally posted by Ronald Anusiewicz View Post
        Is there a way to change this setting using xbasic? I have about 30 computers using the runtime that will need to be changed. Really don't want to have to sit down at each one to change this setting.
        I when and changed the setting in the database with my programming version. I just looked under the runtime and it is showing that it has been changed.

        Comment


        • #5
          Re: A friendly word of warning about the date 01/01/2020

          Looks like this setting is in the registry and is stored at user level. Will see if I can find the key...

          Comment


          • #6
            Re: A friendly word of warning about the date 01/01/2020

            For Alpha Anywhere it's in Computer\HKEY_CURRENT_USER\Software\Alpha Software\Alpha Anywhere 12.0\init\date\date_window#
            Similar path for V11 & V10

            Comment


            • #7
              Re: A friendly word of warning about the date 01/01/2020

              I have a number of work stations connected to a network using the runtime application. I created this function which is to be
              called from the application's autoexec script. The function checks the existing date value and if it is different from the date
              value I want, the registry will be updated. I tested it with version 11 and AA and it appears to be working fine.

              In this example, I'm changing the date value from the default of 20 to 40. The registry value will be "40.000000"

              Code:
              FUNCTION Preferences AS C ( )
              	'sets the 21st century date
              	
              	vcYear = "40"	'enter the 2 digit year
              	vTarget = vcYear + ".000000"
              	
              	vVerNo = version("V")
              	if vVerNo = "12.0" then
              		vVer = "\Alpha Anywhere " + vVerNo
              	else
              		vVer = "\Alpha Five " + vVerNo
              	end if
              	
              	preferences = Registry.sys_get("HKEY_CURRENT_USER\Software\Alpha Software"+vVer+"\init\date\date_window#")
              	IF preferences <> vTarget THEN
              		registry.sys_create("HKEY_CURRENT_USER\Software\Alpha Software"+vVer+"\init\date\date_window#",vTarget)
              	END IF
              END FUNCTION
              Alpha Anywhere v3.5
              Version 12.3, Build 2999
              MySql56 & DBF's

              Alpha 4, 5, Anywhere

              Ron Anusiewicz

              Comment


              • #8
                Re: A friendly word of warning about the date 01/01/2020

                I suppose the only concern would be if not specifying 4 numbers for the year when entering a birthdate since 1940 is still in the valid range...
                Robin

                Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

                Comment


                • #9
                  Re: A friendly word of warning about the date 01/01/2020

                  I didn't realize this was a per/user setting, so when users started to mention the year was reverting to 1920 I was caught off guard this week. I addressed the issue by adding this snippet to the end of my Autoexec. Works in an old version of A5V12

                  Code:
                  dim currentSettings as P
                  dim targetDateWindow as n = 30
                  registry.load_settings("init",currentSettings)
                  
                  if .not. variable_exists("currentSettings.date.date_window") then
                  	currentSettings.date.date_window = 0
                  end if
                  if currentSettings.date.date_window <> targetDateWindow then
                  	dim updateSettings as p
                  	updateSettings.date.date_window = targetDateWindow
                  	registry.save_settings("init",updateSettings)
                  end if
                  The user will have to relaunch the database for the change to take effect. I couldn't figure out a way to force a refresh of the setting short of opening View>settings, which I was trying to avoid. So I force the users to relaunch the database (code not shown).

                  Change "targetDateWindow" to whatever decade you want to cutoff to happen.

                  Comment


                  • #10
                    Re: A friendly word of warning about the date 01/01/2020

                    Jay,
                    Thanks very much for posting the solution.
                    WJG

                    Comment


                    • #11
                      Re: A friendly word of warning about the date 01/01/2020

                      Thanks Ron. I have added a version of this to my autoexec.

                      Bill.

                      Comment

                      Working...
                      X