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

unstable after crash

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

    unstable after crash

    hi again:

    after the null value field displaying a value of 0.00 (previous post) i deleted the field rule for the field and replaced it (simple default expression of 0) and deleted and replaced the field on the form. now it does not have the default value of 0 it is just blank. field rule is set at start of entry.

    much to my dismay i'm now getting frequent a5 engine crashes.

    any help much appreciated!!

    regards,

    ed

    #2
    RE: unstable after crash

    I didn't read all of the other post but it occurs to me that "0" is not a null value. Perhaps you should use 0 as the default to prevent null "" values.

    Russ

    Comment


      #3
      RE: unstable after crash

      hi russ:

      that's the corker! the default field rule value is indeed 0. the value displayed in either the form, default form, or default browse is 0, however if i write a script:

      dim test as n
      test=shipping.value

      and then look at the variable "test" with the debugger it contains a number that is huge.

      i'm going to try adding another field "shipping_1" and not deleting the original, just leaving it there (it is in the middle of the structure).

      thanks for your reply!!

      regards,

      ed

      Comment


        #4
        RE: unstable after crash

        Ed,

        changing the field rule alone will not fill existing records with correct values. The default value will be supplied when you next add a new record, but probably does nothing for your existing records. This experience is illustrating why empty numerics are to be avoided.

        Run an update operation to assign the constant value zero to each numeric field. Or fill them by hand. -- tom

        Comment


          #5
          RE: unstable after crash

          Ed,

          Also, the field rule probably has nothing to do with assigning an actual value to your variable. Presumably your form declares the variable in a script that runs when the form loads. That script should assign a zero value to the variable immediately after it comes into existence.

          -- tom

          Comment


            #6
            RE: unstable after crash

            hi tom:

            thanks for you help as usual.

            i'm doing a thorough review before i respond, but have no brain cells left at this time.

            thanks again, your response alone reduced my blood pressure. you are a scholar and a gentleman ... and there's damn few of us left .. i think we must all be here on this forum.

            thanks again tom, i'll bang away tomorrow!

            regards,

            ed

            Comment


              #7
              RE: unstable after crash

              hi tom:

              i've traced the problem to another form. there is a button on my order entry/fill form that makes a new record in the sale_head before opening the sales_set. for some reason when the new record is created the field rules are not filling in the default values for amount/balance/shipping or gst. the shipping field displayed on the form was corrupt as well, so there was more than one problem. i'll keep on digging into the errant field rules now that i'm on track.

              thanks again tom!!

              regards,

              ed

              Comment


                #8
                RE: unstable after crash

                hi:

                the plot sickens!

                now i get an a5engine.dll crash when i try to get a report from the g.l. which has nothing to do with the sale_head or the sales set.

                this is not good.

                any help is greatly appreciated!

                regards,

                ed

                Comment

                Working...
                X