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

A New Year puzzle...

  • Filter
  • Time
  • Show
Clear All
new posts

  • A New Year puzzle...

    Hi folks

    I'll try to explain this as simply as I can...

    I have an order processing app. The main screen contains customer/order details and there is a region which can show up to 40 product lines on any one order.

    Each product ordered by a customer is made in one of 6 different production workshops. Each product stock record has a field with a single character to designate which production area makes that item.

    I want to be able to e-mail the appropriate parts of the customer's order to the appropriate workshop. I have succeeded in doing this by filtering the "reports" on the single-letter workshop code.

    However, I need to be able to have a field in the order screen which contains details of all the workshops involved in that particular order, e.g. if a customer orders a knife made by workshop A, and a spoon made by workshop D, the field should contain the string "AD". If the order is for two spoons I don't want the field to say "ADD" (although if that can't be avoided I can work round the later manipulation of the field using the $ substring inclusion function).

    Why do I think I want all this? Well, each workshop sends its own finished products to the main packing area, to be combined with goods from the other workshops. The complication is that the company also supplies a range of pre-made products which are simply sold to the customer from stock (all workshops hold the same stocks), and I need a way of including those pre-made products on just ONE of the workshop orders. Customers may order goods made by say, workshop A only, in which case the pre-made goods need adding to A's instructions. Or they may order goods made by workshops A,B,D and F, in which case the pre-made products need to be added to any ONE of the workshops' instructions. Still with me?

    My thoughts are that if I have a field on the order screen which contains, say, "ABDF" to indicate which workshops are involved in that one order, I can manipulate the reports in such a way that I can specify which instructions are sent to which workshop by inspecting the contents of the field. There are also other useful features I can implement once I have my field in place. (Naturally, if the contents of the order are updated/changed at any time, the contents of the field need to be automatically updated too.)

    I would much appreciate any suggestions (or lateral thinking if I'm a bit off-track!). Have spent hours on this and although most of the app is now working well, I just can't seem to crack the "ABDF" field method.

    Many thanks, and a Happy 2005 to all...

  • #2
    RE: A New Year puzzle...

    Hello Paul

    You question is not really clear to me but as you write about you code on the screen and about manipulations of reports.
    Anyway in the stockrecord you have one field for the shopcode A or B or C etc. I would suggest that you make for every shop a seperate numeric field. ShopA, ShopB, ShopC or something like that.
    In the stockrecords alle the fields from ShopA untill FieldF are initially blank or zero.
    Only in one field you enter a 1(one) if the production is made in that shop.

    When you make the fields numeric, you can have a summary in the set.
    Normally displayes as:
    A B C D E F
    0 8 15 0 0 0

    When you can work with calculated fields on your form you must be able to make Calculated fields.
    e.g. SA with the value of “if total_shopA =0,””,A
    Calculated field SB with the value of “if total_fieldB =0,””,B etc
    And displayed your calculatedfields on the screen you’ll find (space) B C (space) (space) (space)

    The adventage using seperate field also allow you to print filtering these fields.

    Good Luck

    Just my 2 cents.

    Ton Spies
    Most things are simple but unfortunately only after the first time