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



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

Sources in Tables

  • Filter
  • Time
  • Show
Clear All
new posts

  • Sources in Tables

    I have a project to combine 13 inter company databases. We need to be able to pull the names by source but also to mail everyone without people getting duplicates, if they're in more than 1 source code. How would you accomplish this in A4v7?

    allan katz

  • #2
    RE: Sources in Tables

    I'll try this one.

    1. If the tables are not in a database format you could import them into microsoft access and immediately export them to .dbf format. Do this with each separate database and do not try to combine them or add fields at this point. Give each database its own different short, descriptive name.

    when you have them all as .dbf format databases, then open each of the 13 database 1 at a time.

    From the main menu of each database use the (D)atabase/Set design command/Reconfigure database/Reconfigure current Database...
    Move the cursor down to the last (blank) field and type in a name for a new field for instance 'dbsource', of type 'character', # of spaces you need for the name of each dbsource. THEN save the field. This name, type, and #of characters should be EXACTLY THE SAME FOR ALL 13 DATABASES.

    From the main menu use (G)lobal update/delete--(U)pdate field--(O)ne-time update
    For field use the name of the last field, the one that you just added 'dbsource'... THEN under expression type a name label for the dbsource you are currently in & hit f10/continue.

    (...Say that you were in the customers database and that it is the database with the longest name. Each Record will now have a field named 'dbsource' that contains the database label 'customers'. The next database would also have added a dbsource field which would contain the name of that database such as 'inventory'...With what we have done so far we can combine all 13 databases and still be able to identify which piece of information was originally located in which database.)

    You also need to rename the fields and regularize the space requirements so that ALL 13 databases have common field names and lengths for the items that are the same. If an Item is not the same, It can be left as is.

    Example fields-- first name, last name, address, customer number etc. BUT WITH the fields that are the same in each database of the same length and name.

    2 more notes.
    1. Names are hard to deal with. If you are attempting to send to people, their names and addresses MUST be the same in all of your databases. (It would not work very well to send Bob Smith, Robert Smith, and Bob Smythe the same information) when they were the exactly the same person, although named differently in different databases.

    It would be well to combine all databases and form a master database of names and delivery addresses. then use social security or some other means to put them back into all 13 databases.

    2. For a quick and dirty solution to the avoiding duplicates, AND AFTER Combining the 13 regularized databases into ONE...

    you may be able to use (U)tilities--(S)ummarize--
    then give a name for a new database, choose the field names that you want to show unique combinations of choose First, and complete this.
    You would then open the new (summary) database, but you would have the social security numbers or name combinations only 1 time not many. Since It is a regular database you could append the original ONE database to it to create only one mailing per individual.

    Hope this helps,


    • #3
      RE: Sources in Tables

      Thanks for much for taking the time to answer my question.
      I've begun to work on this and will implement what you've suggested. I've actually sorted the names alphabetically and assigned numbers to the same people even if they are on the master list more than once. Then I've spread them out into the child databases.

      Allan katz