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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Posting Problem

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Posting Problem

    I am a kidney patient, and have been for the last 24 years (21 of which were at home on a kidney dialysis machine � having had a transplant since). Although a have computer experience, I am not a programmer, however about 8-10 years ago I wrote a database for the Renal technicians for patients and their associated kidney machines in Alpha4v4 (DOS). This worked well until a new PC was required with Windows 2000. I have now been forced to rewrite this with all the new functions\facilities of Alpha 5 in Windows. My problem is as follows:-
    I have a Primary table called machines and a child table called patients as a one to one. These are Dialysis patients who are linked to a single coded kidney dialysis machine. The link field is called machine code, and both tables have a field called surname. I want to be able to either change the machine code to another patient or the patient surname to another machine using the post function on editing either table. It could be the machine has moved to the workshop for repair, or the patient has died or had a transplant. The machine then needs to then be attached to another record\patient etc. The machine table also has further child tables attached, repairs to each machine on a one to many basis etc. Where as, the patient (child) table has water samples on one to many (this relates to samples at their home and not the machine). I originally had these tables all in one set, and have tried since with them split into separate machine and patients.
    DO I HAVE A PROBLEM WITH THE LINK FIELDS OR IS THERE AN EASY WAY TO MAKE THIS POSTING ROUTINE WORK?
    Tags: None
    #2
    RE: Posting Problem

    Ian,

    First - my prayers are with you for what you are going through. Hope you feel better.

    Second, you could zip your application and post it here, so I could take a look at it for you.

    To answer your question, there's no one real way to handle this. It all depends on the application and how you want to do things. Rather than use "Post" within the fields rules, because it has some serious problems, I and others tend to opt for a coded routine, that runs when you save the record or close out of the form. By using this method you can be assured of getting what you want, when you want it.

    If your having problems, I'm sure we can help you. Best thing is to post the zip file and then tell us what you want to do.

    Charlie

    Comment

      #3
      RE: Posting Problem

      Ian,

      Give this some thought. It appears to me that your patients ought to be a single table. Add a field to the patients table called Machine and then use the parent table as a lookup table to fill in the machine field.

      Whenever a patient's machine changes, simply get the new machine via the lookup. Multiple patients could still use the smae machine.

      Perhaps there are other factors in your database that might prevent this but based on your request, that's what I'd try.

      kenn
      TYVM :) kenn

      Knowing what you can achieve will not become reality until you imagine and explore.

      Comment

        #4
        RE: Posting Problem

        Many thanks for your reply.

        I have attached my test files zipped for further advice. If you look at the machine & patient form - having tested it with both a full set called rsch & then a separate set, called machine & patient. The problem is trying to obtain a linked new patient, to a new machine (on a one to one basis), but display (post) the surname & machine code onto each form. i.e. patient 1 has now machine A and patient 2 has what was originally in the workshop or from another patient (may even be patient 1).

        I hope you can understand this, and look forward to your reply.

        Kind regards

        Ian

        Comment

        Previous template Next
        Working...
        X