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

Help with Forms needed...

  • Filter
  • Time
  • Show
Clear All
new posts

  • Help with Forms needed...


    I am working on an application that takes a user-selected external table and copies it to an internal working table called [appropriately enough] “WORKING.DBF.” Because I never know exactly what the file structure of the external tables with which I work will be, my scripts are written using global memory variables that hold certain field names.

    I typically won’t know, for example, what the incoming external table’s name for its address field will be; ADD, ADDR, ADDR1, ADDRESS, STREET, etc. In order not to compromise the final output table’s structure, I map the name of the [in this case] address field (whatever it’s actually called) to a memory variable with which my scripts will work from that point on. This is a common practice in the mailing/data processing industry where one is continually working with strange or foreign tables (or BOTH!).

    I want to create a form, based on the “working” table (I think…), that has a drop-down list (or as many as needed for the variables being mapped) of the fields in the working table that, once selected, would be stored in the assigned memory variable. Currently, I have to launch UI_GET_LIST_ARRAY() from a button alongside the memory variable’s field on the form, and choose a field from there, but I’d like to do it directly from the form.

    Does anyone know if this can be done in A5v4, and if so how?

    Thanks and regards,

    Geoff Hollander

  • #2
    RE: Help with Forms needed...

    Geoff, if I understand you correctly, the field names in WORKING.DBF will always be changing due to the external tables. I wonder if it might be helpful to get the field names from the external table, assign a variable name to each, and then append to WORKING (after removing the old data)using those names. This way, WORKING could always retain the same field names, which might be easier to deal with. Sure, you still have to determine the external names, but this way you'd only have to do it once.

    I realize this doesn't answer your specific question, but it might point you in a different direction that would require a NEW question! (just what you needed, right??)


    • #3
      RE: Help with Forms needed...


      I work with some 75 different file inputs and convert them to a standard output(working.dbf). Each client sends data that matches to the working.dbf to some degree. I have created a parameter file that defines each user's input file. the parameters are fed to the import script. Imports are loaded into an initial dbf that has field are mapped to the working.dbf. Once the import.dbf is loaded its contents are appended to the working.dbf.

      this is a simplification. If you need more information. I will attempt to assemble a miniversion of the application and send it to you.

      bob adler