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

indexes

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

    indexes

    I have a data dase called dispatch.dbf
    one of the fields is called "load" and its a calculated field as: recono("dispatch").
    Sometimes as you enter new records and do a save it duplicates pre-existing record number and duplicates the info in the new record. You end up with mupltiple records with the same number which you can't changes to the correct number. If you do a "C" for change on the duplicate record and enter down thru multiple fields and then do and F9 it then changes that record number to the correct number.

    It's my understanding that you can't have duplicate record numbers in a database.

    This is V1 on XP Pro machines, This problem has only happened since moving to XP Pro, we went many years without this as an issue on win 98

    Any ideas???

    #2
    RE: indexes

    A4V8 is recommended for Win XP and WIN 2000. There are conflicts with earlier versions running under those 2 Operating Systems.

    Please call Customer Service 800-451-1018 for further information.

    gm

    Comment


      #3
      RE: indexes

      Sorry, I sent my earlier message to the wrong board.

      My appologies.

      gm

      Comment


        #4
        RE: indexes

        Using Recno() in a calculated field is NOT anything that you want to do. Recno() is the relative record number from the beginning of the database. As you add and delete records from the database, the recno() changes.

        Example:

        If you have 350 records in a database, the last record number is 350. if you delete 10 records from the middle of the database then pack it, ALL records following those will have NEW record numbers, so now the last recn() is 340. As you haven't changed any of these records, the calculated fields are not affected. so your calculated field of recno() hasn't changed. NOW, you add a new record. it legitamately has a recno() of 341. This is placed into your calculated field.

        GUESS WHAT????? now you have 2 records with a calculated field value of 341.

        The lesson here is pretty simple. Record numbers are dynamic. If you want a unique number for an index, then find some other algorythm. Possibly make it an autoincrement field using some number as a starting point. JUST DON'T USE RECNO().

        Tom

        Comment


          #5
          RE: indexes

          This is NOT an XP Pro issue. It is inherent to the database.

          Tom

          Comment


            #6
            RE: indexes

            Hi Tom,

            Thanks for the reply.This is not an issue with our application as we DO mark records deleted as the loads are completed, but we NEVER do a pack on the base to actually remove records, all records stay in the base, which is archived at the end of the year and we start a new, empty base at the beginning of the new year. This allows us to go back to past years for references as needed.

            Comment


              #7
              RE: indexes

              We have had occurrances where the record pointer gets corrupt. So, it appears that you have multiple records with the same record number, but, in fact, there is only one. For us, this usually manifests itself in a report where one record is repeated over and over on the report, and it must be cancelled.

              To remove the corrupt pointers, I duplicate the database, but not the records or indexes. Then I append the data to the new database. Finally, after verifying that all the correct data is there, I remove the old database and rename the new one. This last step is usually done in windows or dos or whatever, not in Alpha.

              Good luck,

              Tom

              Comment

              Working...
              X