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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Beta-Disappearing numbers

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Beta-Disappearing numbers

    I have found a problem, I think. I have named a table invoice header along with other tables. With invoice header as the parent I have made a set. If I go into invoice header as a table only I can enter a money amountin a field called service_charge(among others) and it stays. In my set if I do the exact same thing then the amount disappears as soon as I press then enter key. Any help is appreciated!
    Tags: None
    #2
    RE: Beta-Disappearing numbers

    David,

    Is this a table which you created? Check to see the tyype of field you created and are there any field rules for the field as well as any changes to the field's properties.

    This has happened to me in v4.5 from time to time and, if m,y memory serves me correctly (yah, I knw, that's a stretch) it had to do with the field type and/or formatting and/or field rules.

    kenn
    TYVM :) kenn

    Knowing what you can achieve will not become reality until you imagine and explore.

    Comment

      #3
      RE: Beta-Disappearing numbers

      Well I checked the field rules and it doesnt look like thats it. I had this problem only in beta and not in 4.5 and I know that I had checked it in both. Of course I could always be mistaken.

      Comment

        #4
        RE: Beta-Disappearing numbers

        David,

        Can you give step by step instructions as to how I or others could duplicate the problem?

        kenn
        TYVM :) kenn

        Knowing what you can achieve will not become reality until you imagine and explore.

        Comment

          #5
          RE: Beta-Disappearing numbers

          Ok, I will attatch this database that i have been playing with. If you try to enter in the field service call or labor you will see what I mean. If you go into the form "Service Call Information" which is from the set you will see what I mean.

          Comment

            #6
            RE: Beta-Disappearing numbers

            Downloaded your file.
            Went to the form "Service Call Information".
            Entered in the field service call or labor - did that, worked fine.

            PG
            Peter
            AlphaBase Solutions, LLC

             [email protected]
            https://www.alphabasesolutions.com

            Comment

              #7
              RE: Beta-Disappearing numbers

              David,

              I downloaded your file and entered data into the Service Call and Labor fields. The data would NOT save in the fields. However, when entering a new record, the data was saved so the problem appears to be with the existing records. Haven't a clue whats causing this.

              kenn
              TYVM :) kenn

              Knowing what you can achieve will not become reality until you imagine and explore.

              Comment

                #8
                RE: Beta-Disappearing numbers

                Well, would we consider this a bug? I hadnt even tried it as a new record because after the service call is performed then we lookup the record and enter the figures. Maybe someone can figure this out. I didnt think I was going crazy!!! Thanks for your help. Now if we can figure out why!

                Comment

                  #9
                  RE: Beta-Disappearing numbers

                  I suspect the bug is in your field rules. I opened your DB, attempted to change the referenced fields and they would reset to zero. I went to field rules and deleted all rules. When I did the test again, everything was fine. Run down your field rules, one by one, if necessary.

                  Comment

                    #10
                    RE: Beta-Disappearing numbers

                    I noticed that it has a problem until you "disconnect" the customer table. Even just changing one of the linking fields to a 'bogus' field (i.e., one that is a matching type but doesn't have any related data) will solve the problem.

                    Also, following up on Steve's point about the field rules, I noticed that some of the field rules are strange. The rules you've specified are OK but some of the tabs that only have the default settings still have a check mark on them. Maybe there is a problem in your data dictionary somewhere and just rebuilding the field rules from scratch will resolve it. (By 'scratch' I mean actually deleting the existing .dd* files for the header and/or customer and then rebuilding the field rules. New data dictionaries will automatically be created once you delete the originals and re-open the table.)

                    Comment

                      #11
                      RE: Beta-Disappearing numbers

                      FWIW,
                      I think the problem is in the customer lookup. You've used 2 customer tables linked to the invoice header and a conditional lookup to the 2 tables. Even though the lookup field rule will allow you to input a mapping for each table, the documentation still reads the same as V4 - only 1 mapping is allowed and both lookup tables must be mapped the same.

                      When in design mode, clicking on the business customer in the mapping window causes errors to be posted to the trace window. Further clue that the problem is here. I think Alpha can't evaluate the lookup field rule and just simply stops.

                      Also, FWIW,
                      Simplify the set and the database: customers are customers; put them both in the same table.

                      Secondly, you only need the customer ID in the invoice header; all other information (address, phone, etc.) can be provided by lookups on the invoice and on reports. You can also delete those fields from the invoice header to simplify the database.

                      Comment

                        #12
                        RE: Beta-Disappearing numbers

                        Well guys I appreciate all the help. This is a database that I am playing with before I really get into the real thing. I just happened to come up with this problem and couldnt figure it out. To my surprize I never suspected field rules to have anything to do with this because these particular fields didnt have much to do with the rest. Also, in my 2 tables, I was just trying something out for fun. Normally, I would only have one customer table. Thanks for all the help.

                        Comment

                        Previous template Next
                        Working...
                        X