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

My invoices are changing!

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

    #31
    Re: My invoices are changing!

    It seems you don't want to post your database for general examination. If you trust someone on the board you might email them and ask them if they will look if emailed to them privately.

    In the meantime, how about a screenshot of your index definitions that are being corrupted, like my attachment.
    There can be only one.

    Comment


      #32
      Re: My invoices are changing!

      There was an issue in the v9 browse in which Alpha would show one record being in focus, but in reality another was. If a delete or edit was done to the record that looked like it was the one in focus--that is, it was "highlighted" and or the row selector chosen, many times a different record was actually in focus and would be deleted or changed...I kid you not.

      This was reported several times for v9 and hopefully has been fixed in v10.....but do know it is an issue yet in v9 (or could be for those who enter/delete data in a particular way).

      Carol,
      Make sure this is not happening to you as I think it is a possibility.
      Last edited by MikeC; 02-02-2010, 11:44 AM.
      Mike
      __________________________________________
      It is only when we forget all our learning that we begin to know.
      It's not what you look at that matters, it's what you see.
      Henry David Thoreau
      __________________________________________



      Comment


        #33
        Re: My invoices are changing!

        I am working with someone privately who has offered to look at it.

        Thanks.

        Carol


        Originally posted by Stan Mathews View Post
        It seems you don't want to post your database for general examination. If you trust someone on the board you might email them and ask them if they will look if emailed to them privately.

        In the meantime, how about a screenshot of your index definitions that are being corrupted, like my attachment.

        Comment


          #34
          Re: My invoices are changing!

          Originally posted by MikeC View Post
          There was an issue in the v9 browse in which Alpha would show one record being in focus, but in reality another was. If a delete or edit was done to the record that looked like it was the one in focus--that is, it was "highlighted" and or the row selector chosen, many times a different record was actually in focus...I kid you not.

          This was reported several times for v9 and hopefully has been fixed in v10.....but do know it is an issue yet in v9 (or could be for those who enter/delete data in a particular way).....
          Heck, that has been a problem since v5 I think. I remember trying to work on a solution to this at a few of the local A5 User Group meetings we had back then. At the time it was repeatable in most of our apps by editing each record then arrowing down to the next one until the last line in the browse was reached - then the next arrow down would take you to the next record but show the record you had just finished editing. I thought this was part of what Alpha was going to be trying to fix with the new browse but I haven't seen any confirmation of that yet. This is also the main reason I've refused for years to allow people to use the browse to add/edit records in any of my apps. As I've said before, new features are wonderful but not unless reliability issues like this are fixed first. (Or, maybe this is just a .dbf issue and can't be fixed by Alpha - if so, tell us so we can quit asking for it to be fixed.)

          If someone can confirm that this is or is not a problem in the new browse, please let us know. At one point it seemed to be working correctly for me but then the same problem seemed to turn up again and there were other issues with the new browse so I went back to the old one - not sure which one I'm using today but think it's still the old one.

          I've also seen a problem recently when opening a form via xbasic and going to a specific line in the browse. Sometimes the correct line appears to be highlighted but A5 is actually on a different line. (Or was it the other way around? Either way, it was a big problem for the users.)
          Last edited by CALocklin; 02-02-2010, 12:03 PM.

          Comment


            #35
            Re: My invoices are changing!

            Cal,
            What I was referring to is in addition to the old problem. See the example I had posted a while back regarding this.....it only manifests itself when a user does very specific actions--the sample illustrates this.

            http://msgboard.alphasoftware.com/al...ocumented+bugs
            Mike
            __________________________________________
            It is only when we forget all our learning that we begin to know.
            It's not what you look at that matters, it's what you see.
            Henry David Thoreau
            __________________________________________



            Comment


              #36
              Re: My invoices are changing!

              Originally posted by MikeC View Post
              What I was referring to is in addition to the old problem. ...
              Oh, wonderful!

              Comment


                #37
                Re: My invoices are changing!

                Hi Carol...
                when i updated to V10 i had similar problems with orderpayments disappearing from their associated orders. i could always get them back by either reindexing or compacting the database but it was VERY unsettling. I REALLY don't like to reindex every day!

                after a lot of grief i think that i traced the problem to one of a few possibilities:
                1) i was using a development application and routinely copied the application files to the test database. on one occassion i copied the data files back to the development database VERY BAD IDEA... much grief!!

                It is unlikely that you are doing this so...

                2) in the previous version of alpha (before all the bad stuff started) i was allowing the user to enter new payments in a form based on the Order==>OrderPay set. (There has been some discussion on the forum re: is this good practice). It worked for 9 years... so i assumed i was ok.

                ... but it seems that i wasn't... at least not when i upgraded. The form was created in V4.5 and the problems stared in V10.

                So.. i locked the form down & prevented payment entry. I used a different strategy to enable payment entry. I placed a button on the form that:
                1) initialized a global variable to contain the Order# (linking key)
                2) close the Order==>OpderPay form
                3) open a new form based on only the OrderPay table. the form was opened in 'enter new record' mode
                4) code activated the Order field & populated it with the Order#
                5) the form is left in the capable hands of the user to enter OrderPay info

                ... There is a button on the OrderPay form that saves the record & reopens that Order==>OrderPay form. The global variable is used to find (not query) the Order# we are working on.

                This has worked for a few months.

                BUT

                it really bugged me that the original 1:many form did not work when i upgraded... so... i created a new form based on the 1:many set. Everything works!

                So... either i have not really solved the problem or the problem has something to do with the form not functioning in the upgrade.

                In any case, the cold chill of missing the payments that were assigned to orders was enough to dissuade me from moving the Orders==>OrderPay form into test or production. I continue to use the rather inelegant 'enter-payments-in-table-not-set' procedure.

                3) i watched the user enter payments. at times they would do a 'search' on the order field... BUT they were really changing the order#!!! VERY bad practice... so i do not allow order numbers to be changed in the form... also i placed a field event on the Order# in OrderPay... if an order has been assigned it cannot be changed.
                From your description i do not think that this is your problem... but you may still want to protect your records in a similar manner.



                hope this helps.

                D

                Comment

                Working...
                X