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

Alpha five on the field

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

  • martinwcole
    replied
    Re: Alpha five on the field

    I think it can be managed with what you have.

    Also, my sense is that you are not fluent enough with Alpha in later versions to do what has been suggested.
    You could hire someone who is very fluent with V12 to do this for you using sql and/or the web version.

    Leave a comment:


  • MoGrace
    replied
    Re: Alpha five on the field

    I doubt there is anything simple about this process if multiple tables are involved that must retain their link(s) to the patient table. It would be good to continue this discussion and have some sample data from the tables involved. I have a few ideas but without a sample app, we are leaving Claudio to figure this out on his own...

    Leave a comment:


  • DaveM
    replied
    Re: Alpha five on the field

    A not so simple append operation would take care of it.
    copy the "in the field data" to another folder and append the records to the office db. Use unique. sounds like the id field is not the way to go, but id+lname should work.

    I am assuming dbf files. Process would be a bit different with sql
    Last edited by DaveM; 05-28-2019, 04:22 PM.

    Leave a comment:


  • Mike Wilson
    replied
    Re: Alpha five on the field

    Hello Claudio,
    What you have described I interpret as this:
    1. The work in the field will result in ENTERING NEW PATIENTS NOT UPDATING EXISTING PATIENTS to the database on the field computer.
    2. The work in the office could do both.
    3. The conflict you are concerned with is the possibility that two different people might be entered as new patients and have the same patienID and therefore the records are not unique to the auto-increment number.

    UNCERTAINTY: You wrote:
    "If he does a simple backup he will overwrite the records on the main database in the office". I am uncertain what you are actually doing when you use the term "simple backup". Are you intending to say "Update" or "Append" to the office database with the field computer records?

    There are several possible solutions, but it matters what method you are using the transfer records from your field computer to your office database. And "simple" is relative.

    Leave a comment:


  • CharlesParker
    replied
    Re: Alpha five on the field

    I think the upgrade is worth it - but be very aware that you will want to recalculate your controls and test your application knowing that A LOT has changed and your application may not work as expected on first run. You may have some tweaking to do. I have seen where you might have to rebuild the same component from scratch but again, I think there are probably a lot of people who had zero issues. Good luck, and again I think for what your looking to do the upgrade will be worth it but there will be a learning curve!

    Leave a comment:


  • Ted Giles
    replied
    Re: Alpha five on the field

    I did this for the UK NHS years ago.
    The easiest way is to;
    Export the records the partner needs to take away with them.
    Lock those records to prevent update.
    When partner returns, upload previously exported records after taking off the lock - changes will be applied or if no change, then the record stays the same.

    However, this does mean that none of the exported records can be changed until they are put back.

    New records are a different issue. I would suggest a temporary new patient ID which can be changed during the reimport process.

    If you need to do off line stuff, then you will need a web based app to run in offline mode of the device of choice I think you will find.
    Desk top doesn't do off line easily.

    Off line will give the same problems unless the Synch is robust.

    Leave a comment:


  • clipikt
    replied
    Re: Alpha five on the field

    Thanks Charles for your reply. The aplication was developed with V9 but if the current version (12) has the
    tools for doing this offline update i would consider upgrading.

    Leave a comment:


  • CharlesParker
    replied
    Re: Alpha five on the field

    Using a version of AS that does NOT include offline capabilities: Probably what you should do is run some xbasic to do an SQL insert when you save. If you were running Alpha Anywhere this could all be handled fairly well with the built in offline functionality. I don't know how you would handle an edit to an existing record offline without a lot of comparing & accepting of edits, either theirs or yours...then using xbasic perform an SQL update
    If you're on a newer version that included offline capabilities, then you'll want to state the exact version your on. I don't know that it would make too much of a difference but often it does.

    Leave a comment:


  • clipikt
    started a topic Alpha five on the field

    Alpha five on the field

    Hello. Long ago I developed an application with alphafive (9 for windows) for a friend he recently asked for a feature update.
    He is a doctor that work with a partner at small office. The application I developed is basically a database with medical history of patients.
    The problem is that one of the doctors sometimes goes out in the field to remote locations in other villages without reliable internet connections.
    So he wants to use the app on the field to enter information for new patients then go back in the office and update the office database with the new records.
    In the past he handle this with a simple backup utility, but now a partner might be in the office using the database and enter new patients or updating old ones.
    So in summary, what is the best pratice to update just the new records collected on the field on the main database. The main field now is patienID which is autoincremental
    Imagine that the last patient was number 5780. Then doctor goes in the field and open a new record for patient 5781 while the other doctor in the office do the same with a new patient which
    will have the same 5781 id. If he does a simple backup he will overwritte the records on the main database in the office.

    I am sure this is a basic feature, but I have not done any database development in years and now trying to help out a friend.
    Thanks so much for your suggestions!!
Working...
X