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

Vers 6.20 Unique Keys problem ???

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

    Vers 6.20 Unique Keys problem ???

    This is a repost of a msg. I wrote last week or so, but no one responded.
    I'm having trouble with all my copies of Alpha4v6.20 in that they are not recognizing 'Unique keys' when printing reports. I've tried different apps, too, with the same problems. HELP! (Please!)

    Here's my original post:

    Hi, all! I'm having a problem that when printing lables I get multiple copies of some labels. It's an application that I developed several years ago in A4V3 and some offices moved on to A4v6.
    This has to do with a set with related tables, and I'm selecting names based on a child table.
    It is currently working in the one office with A4v3. It has to do with the 'Unique Keys' choice in the range settings when I type 'P'rint 'M'ailing labels. It no longer works in version 6.20.
    I've reindexed the files but that hasn't changed anything.
    Can someone please shed some light on this? Is there a bug in 6.20 regarding Unique Keys?
    Btw, these are all multi-user versions running from a netware server with netware clients, Win98.
    This appears to be the only thing wrong since moving up to 6.20 several months ago. (and they only told me about it now!)
    If I can provide more info to help figure this one out, please let me know.
    Regards,
    Pete Cantele
    Diocese of Joliet, IL



    #2
    RE: Vers 6.20 Unique Keys problem ???

    Pete:

    I just tested 'Unique Keys' option (as 'Yes') on the range card and it worked as advertised. I am using A4v6.2. The test that I did was on a simple stand-alone db - not a set. Is it possible that for some reason, this set's duplicate records are possibly showing up in the mail label - sort range.

    For example, My name is Herrold. The index in these 1250 records is on 'Last name'. When I ran the range with Last Name as the index, only the first 'herrold' (Betty) showed up in preview. If this were child in a set, there may be many 'first and unique' records generated by the set all of them 'Betty', for instance as the first name. Is this what's happening to your sort? I.E. are the duplicates the same guy?

    I haven't been in Ver3 for so long I can't remember differences any more. But these are my findings.

    Let me know how you do. I still have ideas.

    Ken

    Comment


      #3
      RE: Vers 6.20 Unique Keys problem ???

      Ken,
      Thanks for the help.
      I've tried an experiment on another app, too, with the same results.
      With the labels app, I have the following layout:

      ALMASTER ;Unique Card No., Name, Add., etc.
      |=====>ALCODES ;table with Card No. and Code
      |------>ALPRF ;table with codes and 'selected' field

      I run labels based on the Codes in the ALPRF table that have the SELECT field marked true.
      The key I'm using is ZIP+CARDNO, the zip code plus the unique card number. (I've reindexed several times, too).
      Examining the keys with a hex viewer, I can see that the keys are indeed unique.
      Also, I've tried another app. with the same type of experiment. Same strange failure.
      I thought it could be the copy of Alpha I have installed; it still may be. I have a copy on my machine as well as on the server that is shared. Maybe I should try reinstalling on a standalone machine?
      Evidently, others are using it and it's working, so I must have something wrong here. I just never noticed this anomaly before.
      I'd be glad to hear any more thoughts. Again, thanks so much. This is a puzzler for me.

      Regards,
      Pete Cantele

      Comment


        #4
        RE: Vers 6.20 Unique Keys problem ???

        Nuts, the layout of the SET did not come out right when I pasted it in here. Here it is again:

        ALMASTER
        .....|=====>ALCODE
        ..............|----->ALPRF

        Ok? Hope this clears that up.
        Pete

        Comment


          #5
          RE: Vers 6.20 Unique Keys problem ???

          For the time being, I worked around the problem by setting up the script to tell the range/print routine to use 'Unique keys' and 'Custom Links' instead of 'Use Set Links'. The set links were a one-to-many link with the target set to 'all'. I used a 'custom' link to say just to use the first.
          I don't have to do this in Version 3. Have I missed something over the years? :)

          Comment


            #6
            RE: Vers 6.20 Unique Keys problem ???

            Pete:

            G R E A T!

            We all learned something here. I figured that the duplicate was something to do with the multiple records duplicated in a set, bot for the life of me I didn't kow about the options you just found --- GEEZE ever 8 years experience gets a new lesson each day.

            Thanx

            ken

            Comment


              #7
              RE: Vers 6.20 Unique Keys problem ???

              If the link set to first corrected the problem then the problem was in the first place virtual records. They are unique in the sense that each is attached to a different child. It's explained in the manual.

              Russ

              Comment


                #8
                RE: Vers 6.20 Unique Keys problem ???

                Wait a Minute Russ.......What's a Manual? Ha

                Ken

                Comment


                  #9
                  RE: Vers 6.20 Unique Keys problem ???

                  Thanks for the post.
                  Well, linking to "first" only worked for that situation. I need it linked to "all".
                  Linking to 'all' and then specifying 'Unique Records' worked like a charm in version 3. (and still does, btw).
                  I can't for the life of me figure out why it doesn't work in version 6.
                  For example, I have 3 tables; Names, Codes, and Profiles.
                  Names contains:
                  Cardno Char.
                  Name Char.
                  Address Char.
                  Zip Char.
                  etc.

                  Codes contains:
                  Cardno Char.
                  Code Char.

                  Profiles contains:
                  Code Char.
                  Description Char.
                  Selected Logical Codes (one name, many codes per name)
                  ............|----> Profiles (only one profile per code)

                  Ok, now I have an index in Names of "Zip+Name". This is the index I'm using to print my report/labels.
                  My understanding is that when I select 'Unique Keys', I'm referring to the unique key indicated by "Zip+Name", correct? If so, why doesn't this work?
                  What I'm talking about here is the Range Settings when you go to print a report/mail labels.
                  I just tried it again with a new index and it STILL doesn't work. I'm baffled. Works fine in the Alpha4 version 3 we have.
                  Any thoughts please help. Are you able to try something like this and have it work? I'd be glad to send abreviated data to anyone willing to check it out.
                  TIA.
                  Pete

                  Comment


                    #10
                    RE: Vers 6.20 Unique Keys problem ???

                    Pete:

                    I'm home nursing a cold for the week and weekend and have some time. I's be glad to look at your zip and see what can be done. Go for it.

                    Frankly, I avoid range settings in A4v6 reports preferring to do the in a different, less confusing way. At the report editor, select [F7] then '"R"ecord selections and print settings'. Use the right arrow on the first item, "method for selecting...." -- take all the defaults and build your search criteria on the top line in the lower section This is titled 'Search Expression'........ A4V6 does a quick dynamic search and you don't take the chance of leaving the db in a range like Sharon Harriss is suffering right now.

                    If that doesn't handle the 'virtual record duplicates' I then isolate the linking child and make it the header of a second set. After all it IS the one I want all the information on.

                    Just some thoughts in the meantime.

                    I'll glady help any way I can and feel that I am able.

                    Ken

                    Comment

                    Working...
                    X