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

Lookups, PREVIOUS records, different twist.

  • Filter
  • Time
  • Show
Clear All
new posts

  • Lookups, PREVIOUS records, different twist.


    SET with files - daily, vehicle, driver and fuel. FILES in question - daily and fuel. These 2 files are joined on the vehicle number field. Both contain date fields.

    NEED TO DO - The daily file records fuel data on a fillup basis which is not necessarily a daily basis (it could be more than once per day, or, every other day, etc. The fuel file contains fields for date, odometer reading, gallons purchased and purchase cost. I need to be able to have the program place the the PREVIOUS fuel:odometer reading into daily:prev_odo field with the record pointer set to the same vehicle number for the current daily record (new record being created). The prev_odo field would have to be a creation field and not change if you edited the field later. This data would allow the calculation of MPG among other things and would relieve the driver of having to accurately remember the previous odometer reading for perhaps days. The drivers also change vehicles frequently, creating additional problem.

    Drivers report on their daily/vehicle activity on a daily basis, because of internal accuracy and volumn problems

    Any good way to do this in 3.04 without a ton of xbasic which might create on-site maintenance problems for me? They are about 35 miles from me and not at all computer literate.

    Thank You

    Ron Cottrell

  • #2
    RE: Lookups, PREVIOUS records, different twist.

    Tried using a script using the object THIS and an event of OnArrive. The script consisted of QuickSort on THIS and FetchLast on THIS. This produced no result or errors. When I returned to the script, it was gone!

    Any suggestions?



    • #3
      RE: Lookups, PREVIOUS records, different twist.

      Hi Ron,
      No, I don't have any ideas for the script, but I remember years ago in Alpha four.v1 creating a checking account database where the balance forward was the balance field of the previous record. So, are there too many vehicles to have one database (table, now-a-days) per vehicle? If so, when entering the amounts (gallons, price, etc.), you can create an index on descending record order, then have the previous record automatically fill in the current record with whatever you need to "carry forward", so to speak.

      Just an idea that worked for me for a checking account.


      • #4
        RE: Lookups, PREVIOUS records, different twist.

        Hi Wanda,

        Thanks for the reply. Your idea is sound but . . .! This system is to be used by neophytes so I'm trying to keep it as simple as possible. I'm afraid that so many dbf's might overburden the already overburdened.

        I solved the problem by using Lotus Approach 9.1 as I have done with three previous apps which I have attempted with Alpha 5. I Have officially given up on Alpha 5 and have sold the package. The reasons are simple, lack of documentation and support.

        Thanks again for your help.