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

Date Format In Script

  • Filter
  • Time
  • Show
Clear All
new posts

    Date Format In Script

    I have written a script that automatically updates a "Revision Date" when a record is saved. Works fine on a few computers in the Network, most others it fails with an error message reading "tbl.Update subelement is of different type".

    Tried changing the date format in the problem systems from d/mm/yr to m/dd/yr with no success. Am using Date() function without curly brackets in the Field_Value_Put statement.

    Any great ideas here? I'm baffled!

    RE: Date Format In Script

    Check field rules for a conflict bwtween field rules for the date field and the scripted update. I have had a conflict here where a field is 'calculated' and I have a rule for it. The script update will not work where the field rule is set.
    Does not explain why only some stations are encountering the problem.....


      RE: Date Format In Script


      have the other work stations run network optimize? they may be out of sync with those that are working.

      bob adler


        RE: Date Format In Script

        Tried optimize and drop kicking the other stations to no avail.


          RE: Date Format In Script

          John, throw a copy of the script up here so we can see whats happening, or not happening in this case.



            RE: Date Format In Script

            Here's the script I am having the problem with. Seems to only work on my computer and nobody else's on the network. Any great ideas anywhere?

            'Set Update Value To Current Date






              RE: Date Format In Script

              I hate to do this but I'm going to make a suggestion I haven't tested. I would suggest using form commands only:

              tbl=table.current() '-- NO LONGER NECESSARY


              :Clients:Update.value = date() '-- OPTION: ...Update.text = dtoc(date())


              Also, your existing script might work if you put a Parentform.resynch() after the Change_end() command.


                RE: Date Format In Script

                You mentioned that the script runs when you save a record. Exactly which event is it attached to? Is it a field rule event or a form event? I once placed a similar script on the CanSaveRecord field rule event and the change_begin bombed if a change had already begun. Same script worked ok on the OnSaveRecord Event. Similar problem if it was attached to the equivalent form events. I also added some lines to check the mode at save to react differently if the script fired before all of the child records were saved. This was on a large set with a number of child records. Example below:

                tbl1 = table.current(1)
                if tbl1.mode_get()>0
                tbl1.Date_Edit = date()
                tbl1.Date_Edit = date()
                end if

                This has never given a problem on a number of different computers. I don't know if this is relayted to your problem but it is another area to investigate.