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

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

A_Case-> in calc expressions on forms.

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

  • Michael Humby
    replied
    Re: A_Case-> in calc expressions on forms.

    Ray,

    Thanks for your input, I can live with the A_case bug if it is only during development but I need reassuring that the bug will not creep in during runtime.

    The reason I am stuck with the October 2008 builds because I have a serious slow down in some areas that have run perfectly in the past on all versions and on all V9 builds, that is up until October 7th. It was the next build that claimed to fix the A_case where my problems began and I am certain that it is to do with changes made to fix the A_case bug. I waste hours testing these new build when they are posted.

    This is nothing to do with the browse bugs or A_Doc addin because I have never used it. I sent Alpha a sample app way back in October that proves the point when running in old builds everything is OK but after October 7th it slows down to be unusable. I am waiting for the dust to settle with the V9 browse updates before reporting again.

    Michael

    Leave a comment:


  • Raymond Lyons
    replied
    Re: A_Case-> in calc expressions on forms.

    Michael,

    At some point after 1772-3208 I stopped getting this problem (but knock on wood). If you have a deployed version that does not already have A_Case messing things up, it should never just arise there via using the runtime. I believe it has to arise during development. But of course if does come up in developing, say, an update to a deployed app and it isn't fixed, then it will be in the update. But as stated elsewhere in this thread, it is not all that hard to deal with.

    If there are other bugs that have not been resolved (keeping you from updating), be sure to let Alpha know about them.

    Ray

    Leave a comment:


  • Michael Humby
    replied
    Re: A_Case-> in calc expressions on forms.

    Thanks John, not too sure if I'd be able to use one of your fetch scripts though because these are custom calculations that appear in the properties of my forms/reports, not the scripts.

    This bug appeared in the calculations of a specific form. Anyone know if this bug spreads to all other forms or if it is isolated to just the occasional form?

    Michael.

    Leave a comment:


  • fsi
    replied
    Re: A_Case-> in calc expressions on forms.

    As for me (and thus my advice), there was no suggestion forwarded that led to a definitive solution. All this talk about A5Doc - and I don't have A5Doc! So, as stated in my last post, I moved toward a manual fetch. Not that big a deal, really, and I wrote it such that it's a general calculation script.

    I am well aware of Murphy's Law. I chose to not risk the gamble on A5 to behave properly after deployment. As I said, the manual fetch and fetch next loop isn't that big a deal. In fact, it took less time to create my own calc script than was spent trying to get the built-in calc to work reliably. Now I sleep with confidence.

    Leave a comment:


  • Michael Humby
    replied
    Re: A_Case-> in calc expressions on forms.

    I've just been hit by the A_case calculations bug, admittedly I am using an October build prior to the supposed fix. (I am using this build because of various other bugs in later builds that have not been resolved.)

    What I'd like to know is - does the bug only occur during development, or can this bug re-occur once my application has been deployed using the runtime?

    If the bug does only occur during development then I handle that, but if it crops up again during runtime use then I've got problems because there's not much I can do once my customers have the application.

    Any help would be appreciated,

    Regards,

    Michael.

    Leave a comment:


  • JPFromtally
    replied
    Re: A_Case-> in calc expressions on forms.

    Ok..... I think I got it working... Here are the steps:

    1. Install latest update... For some reason, A5 was not letting me know in the startup screen that there was an update available.
    2. Delete the A_Case statements in the Calc dialog (not the expression builder!)
    3. Save and restart a5.
    Last edited by JPFromtally; November 05, 2008, 10:53 PM.

    Leave a comment:


  • Bill Parker
    replied
    Re: A_Case-> in calc expressions on forms.

    Bill H. is right. A5Doc is not the culprit, it was just a messenger. A few posts earlier in this same thread, here, I posted the code in A5Doc that triggered the problem. With Bill identifying that the problem could be produced by A5Doc, I traced through to identify the code, and sent it to Alpha. They said they would fix it, and it seems they did.

    It now seems there may be other causes of the problem as well. So if anyone can find a way to reliably reproduce it, send it to Alpha and I expect they will respond as positively as they did to this case.

    Bill.

    Leave a comment:


  • whanigsberg
    replied
    Re: A_Case-> in calc expressions on forms.

    I tested for the issue by running A5doc against the application and A_case does not recur. There was never a "problem with with A5_doc". Rather, A5doc happened to use a legitimate Alpha5 method which produced the issue which is why I employed it to test the patch.

    Leave a comment:


  • Ed Merritt
    replied
    Re: A_Case-> in calc expressions on forms.

    William, I've been having the same problem with the A_CASE thing showing up, but just today I realized that the culprit has to be the A5_Doc app. I have a folder of files for my order management system, and have copied the entire folder to another folder where I test out any new changes, etc., before doing it live. I did install A5_Doc in that second folder and that's where I'm seeing the problem. The original production files are fine and have not had that problem.

    I would suggest to all who read this to delete the A5_Doc until a solution to the problem is available.

    Leave a comment:


  • Ed Merritt
    replied
    Re: A_Case-> in calc expressions on forms.

    Cal, I have seen the same problem, as have many others. I turned up a post by someone, don't remember who, that suggested fixing the errors, saving everthing then restarting A5. That seemed to work for me. I also installed the patch this week, and so far haven't seen the A_Case bug.

    Seems to be some kind of memory management problem, not that Alpha has ever had that before........Can you say "granular crash" ??

    Update:

    I've realized this morning that it seems to be the A5_Doc app that is causing the problem. Please read my other response regarding this issue in this thread.
    Last edited by Ed Merritt; November 01, 2008, 02:49 PM.

    Leave a comment:


  • whanigsberg
    replied
    Re: A_Case-> in calc expressions on forms.

    I must say that the recent patch solves the A->case issue for me. At least the one action by which I was able to reliably reproduce it no longer does so. If you posted a demo others could look at it.

    And of course you could send it to the company.

    Leave a comment:


  • fsi
    replied
    Re: A_Case-> in calc expressions on forms.

    I'm getting no relief with that approach.

    A5 simply muscles it back to the same old statement:
    *BAD_EXPR dbsum("Ledger","Account",A_CASE->Account_Id,"Payment")

    I see a manual fetch loop and calculation in my future.

    Leave a comment:


  • CALocklin
    replied
    Re: A_Case-> in calc expressions on forms.

    Obviously I have no idea why the new release didn't fix it but don't just delete the A_Case->. Instead, change it to the name of the parent table.

    EXAMPLE:
    If you have a form based on a set where the parent table is Invoice_Header and a field reference in your expression is A_Case->Inv_Ttlf, change it to Invoice_Header->Inv_Ttlf.

    That should give you some relief until Alpha gets it fixed completely. Until that happens, just don't forget to include the table name the next time you build an expression that refers to a field in the parent table.

    Leave a comment:


  • fsi
    replied
    Re: A_Case-> in calc expressions on forms.

    Did I misinterpret release notes for October 30ths 1817-3212?? Was this release supposed to resolve the A_CASE issue for calculated fields (expressions)??

    I'm not using A5Doc, have patched to 1817-3212, still seeing same problem.

    If this patch really fixes the problem, what more must I do? I have already edited the expressions, removed the A_CASE, and saved again, but issue pops up again immediately.

    Leave a comment:


  • Raymond Lyons
    replied
    Re: A_Case-> in calc expressions on forms.

    I still had the A_CASE-> problem with 1772-3208 and submitted a bug report with my best guess as to how to replicate it. Got this response from Selwyn: " ok, this should be fixed now. thanks." Of course "now" will mean the next patch. Let's hope the problem will then be history.

    Ray

    Leave a comment:

Working...
X